Threats / Microsoft / CVE-2022-41040
CVE-2022-41040
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
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-303Ransomware use Flagged3EPSS 0.99945 (verify live)4Exploit Weaponized · public PoC5
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
50 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.99945 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Microsoft, Exchange Server. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-918 Server-Side Request Forgery (SSRF).CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
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