Threats / Microsoft / CVE-2022-41082
CVE-2022-41082
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
Microsoft Exchange Server vulnerability
Microsoft Exchange Server vulnerability allowing authenticated remote code execution, chainable with CVE-2022-41040. Actively exploited in ransomware campaigns.
Verdict
Today item, not a backlog item.
Critical remote code execution in Exchange Server via authentication bypass chain. High EPSS score and confirmed wild exploitation indicate immediate threat to email infrastructure and downstream network compromise.
CISA KEV Yes · 2022-09-305Ransomware use Flagged5EPSS 0.9997 (verify live)6Exploit Weaponized · public PoC7CVSS 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
577 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.9997 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8 (CVSS:3.1/AV:A/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-502 Deserialization of Untrusted Data — weakness family: Injection.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 exploit CVE-2022-41040 to bypass authentication and gain initial access to the Exchange Server.
Business
Email infrastructure becomes entry point for network intrusion without credential compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I chain the authentication bypass with CVE-2022-41082 to achieve remote code execution on the server.
Business
Attacker gains arbitrary code execution within trusted email infrastructure with system privileges.
3
Lateral reach — past segmentation narrative 3
Attacker
I execute ransomware payload or establish persistent backdoor access to the compromised Exchange Server.
Business
Email services disrupted; ransomware deployed across organization; data exfiltration and encryption occur.
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