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

Microsoft Exchange Server vulnerability

Microsoft Exchange Server remote code execution vulnerability exploited in the wild as part of the ProxyLogon attack chain, enabling unauthorized system compromise.

Verdict

Today item, not a backlog item.

Critical remote code execution in Exchange Server with active exploitation and ransomware deployment. Immediate patching required for all affected installations.

CISA KEV Yes · 2021-11-033Ransomware use Flagged3EPSS 0.89509 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
48 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 2021-11-03), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.89509 — 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
02

Who’s exploiting it?

— attribution turns risk into urgency
HAFNIUM State-sponsored (PRC)

CISA's AA21-062A and the Microsoft Threat Intelligence Center attribute the ProxyLogon Exchange exploitation chain to HAFNIUM (now tracked as Silk Typhoon), a state-sponsored group assessed to operate out of the PRC, naming both the group and the Exchange CVEs.10

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
Gain unauthenticated access to Exchange Server through pre-authentication vulnerability.
Business
Attacker establishes initial foothold without valid credentials, bypassing primary security controls.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
Execute arbitrary code on the Exchange Server with system privileges.
Business
Complete compromise of email infrastructure and underlying server, enabling data theft and lateral movement.
3

Lateral reach — past segmentation narrative 3

Attacker
Deploy ransomware or persistence mechanisms across the compromised environment.
Business
Operational disruption, data encryption, extortion demands, and potential regulatory violations from data exposure.
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)
  • 48 reported-exploitation source(s)
  • 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.