basicsecurity.net
Proof, not just disclosure.
Threats / Microsoft / CVE-2023-21529
CVE-2023-21529 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-07

Microsoft Exchange Server vulnerability

Microsoft Exchange Server deserialization vulnerability allows authenticated attackers to execute arbitrary code remotely via untrusted data processing.

Verdict

Today item, not a backlog item.

An authenticated attacker can exploit unsafe deserialization in Exchange Server to achieve remote code execution. This vulnerability has been actively exploited in ransomware campaigns and poses significant risk to email infrastructure.

CISA KEV Yes · 2026-04-133Ransomware use Flagged3EPSS 0.27044 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-13), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.27044 — 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 threat-actor attribution is established from the public feed 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 authenticate to the Exchange Server using valid credentials or through a compromised account.
Business
Legitimate user accounts or service credentials become attack vectors, bypassing perimeter defenses.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I craft a malicious serialized object and send it to the server for deserialization processing.
Business
Standard input validation fails to detect weaponized data structures embedded in normal protocol traffic.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code on the Exchange Server with the privileges of the service account.
Business
The attacker gains control of critical email infrastructure and can access all organizational communications.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence and move laterally through the network to deploy ransomware or exfiltrate data.
Business
Email systems become staging points for enterprise-wide compromise, leading to operational shutdown and data breach.
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)
  • CWE weakness mapping (NVD)
  • 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.