Threats / Microsoft / CVE-2022-41040
CVE-2022-41040
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
Microsoft Exchange Server vulnerability
Microsoft Exchange Server vulnerability allowing server-side request forgery (SSRF), tracked as ProxyNotShell. Chainable with CVE-2022-41082 for remote code execution. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical remote code execution risk via SSRF chaining. High exploitation prevalence in wild with ransomware deployment. Requires immediate patching of all Exchange Server instances to prevent unauthorized access and data compromise.
CISA KEV Yes · 2022-09-305Ransomware use Flagged5EPSS 0.99956 (verify live)6Exploit Weaponized · public PoC7CVSS 8.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
51 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-09-30), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99956 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C) · Affected: Microsoft, Exchange Server. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-918 Server-Side Request Forgery (SSRF).CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog the same day the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request that exploits the SSRF flaw to bypass authentication and access internal Exchange resources.
Business
Attacker gains unauthorized access to email infrastructure without valid credentials, bypassing perimeter security controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I chain this SSRF vulnerability with CVE-2022-41082 to achieve remote code execution on the Exchange Server.
Business
Attacker executes arbitrary code with Exchange service privileges, enabling full system compromise and lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware or data exfiltration tools across the compromised Exchange infrastructure.
Business
Organization experiences operational shutdown, data theft, and financial extortion demands from ransomware operators.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by microsoftCNA
Credited with finding itDA-0x43-Dx4-DA-Hx2-Tx2-TP-S-Q from GTSC working with Trend Micro Zero Day Initiativefinder
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.