basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2022-41082
CVE-2022-41082 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

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-303Ransomware use Flagged3EPSS 0.99964 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit 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
552 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.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.99964 — 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.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 552 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by microsoft (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by microsoftCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.