CVE Intelligence
Skip to main content
CISA KEVRansomwarehighSSRFpublic exploit

CVE-2022-41040

Microsoft Exchange Server Elevation of Privilege Vulnerability

Microsoft Exchange Server Elevation of Privilege Vulnerability

Published Updated Sources: NVD, Microsoft (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, Microsoft MSRC

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Sep 30, 2022

EPSS

100%

top of FIRST's scoreset

Affects

Microsoft

10 products listed

CVSS base

8.8

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Apply Microsoft security update KB5019758 (2022-Sep release) — https://www.microsoft.com/download/details.aspx?familyid=124eeb2b-4066-459e-9416-ee98683f4997.

CISA required action

Apply updates per vendor instructions.

Federal deadline Oct 21, 2022 — passed 1,405 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
MicrosoftMicrosoft Exchange Server 2013 Cumulative Update 2315.00.0 to < 15.00.1497.044Vulnerable
MicrosoftMicrosoft Exchange Server 2016 Cumulative Update 2215.0.0 to < 15.01.2375.037Vulnerable
MicrosoftMicrosoft Exchange Server 2019 Cumulative Update 1115.02.0 to < 15.02.0986.036Vulnerable
MicrosoftMicrosoft Exchange Server 2019 Cumulative Update 1215.02.0 to < 15.02.1118.020Vulnerable
MicrosoftMicrosoft Exchange Server 2016 Cumulative Update 2315.01.0 to < 15.01.2507.016Vulnerable
MicrosoftMicrosoft Exchange Server 2013 Cumulative Update 23Vulnerable
MicrosoftMicrosoft Exchange Server 2016 Cumulative Update 22Vulnerable
MicrosoftMicrosoft Exchange Server 2019 Cumulative Update 11Vulnerable
MicrosoftMicrosoft Exchange Server 2019 Cumulative Update 12Vulnerable
MicrosoftMicrosoft Exchange Server 2016 Cumulative Update 23Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1high2.85.9Microsoft (CNA), GHSA
8.8CVSS 3.1highMicrosoft (CNA), Microsoft

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

  • CWE-918Server-Side Request Forgery (SSRF)
  • CWE-269Improper Privilege Management

Inferred from the weakness class — not observed against this CVE.

CAPEC-664 · Server Side Request Forgery
  • T1548Abuse Elevation Control Mechanism

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

Sep 30, 2022

Federal deadline

Oct 21, 2022

passed 1,405 days ago

Ransomware use

Known

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

49

2 of the 5 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Microsoft Exchange Server 2013 Cumulative Update 23, Microsoft Exchange Server 2016 Cumulative Update 22, Microsoft Exchange Server 2019 Cumulative Update 11, Microsoft Exchange Server 2019 Cumulative Update 12, Microsoft Exchange Server 2016 Cumulative Update 23.
  • Monitor for scanner or exploit-pattern traffic after 49 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPScloud metadata access logsegress proxy logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 8.8 (AV:N)

    Jun 17, 2026 · NVD

  3. 2022
  4. Added · GHSA-6ph7-8wxv-6gf2 published (high)

    Oct 4, 2022 · GitHub Security Advisory

  5. Initial · CVE published

    Oct 3, 2022 · NVD

  6. Added to CISA KEV catalog

    Sep 30, 2022 · CISA

References

15 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2022-41040 is Microsoft Exchange Server Elevation of Privilege Vulnerability, a high vulnerability affecting Microsoft Exchange Server 2013 Cumulative Update 23, Microsoft Exchange Server 2016 Cumulative Update 22, Microsoft Exchange Server 2019 Cumulative Update 11, Microsoft Exchange Server 2019 Cumulative Update 12, Microsoft Exchange Server 2016 Cumulative Update 23 from Microsoft. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 49 public PoC repositories reported; 2 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 100% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.