Threats / Microsoft / CVE-2023-21529
CVE-2023-21529
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-02
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-135Ransomware use Flagged5EPSS 0.62104 (verify live)6CVSS 8.83CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
2 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 2026-04-13), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.62104 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/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 — CNA-assigned (CVE.org); 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 1154 days after 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.
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 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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by microsoftCNA
Credited with finding itPiotr Bazydlo (@chudypb) of Trend Micro Zero Day Initiativefinderzcgonvh with 360 noah labfinder
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.