Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2023-21529: Microsoft Exchange Server Deserialization of Untrusted Data RCE

Published Feb 14, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.8High · v3.1
EPSS59.3%99th percentile
CISA KEVYesAdded Apr 13, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2023-21529CWE-502 · Deserialization of Untrusted Data

CVE-2023-21529 is a remote code execution vulnerability in Microsoft Exchange Server caused by deserialization of untrusted data. The flaw affects supported on-premises Exchange Server releases including Exchange Server 2013 CU23, Exchange Server 2016 CU23, and Exchange Server 2019 CU11 and CU12. An authenticated attacker can manipulate how Exchange Server processes crafted serialized data, leading the server to deserialize attacker-controlled input and execute arbitrary code in the context of the Exchange environment. Microsoft classified the issue as likely to be exploited, and later reporting confirmed active exploitation in the wild, including use by Storm-1175.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution on the vulnerable Exchange Server. Because Exchange is a high-value, centrally connected enterprise service, compromise can provide deep access to sensitive corporate communications and create a strong foothold for follow-on intrusion activity. Reported real-world exploitation has been associated with initial access, data theft, and ransomware deployment, including Medusa operations attributed to Storm-1175.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of on-premises Exchange systems by limiting access to trusted networks and administrative users, isolating internet-facing Exchange infrastructure behind appropriate reverse proxy, WAF, or DMZ controls where operationally feasible, and aggressively monitoring Exchange for suspicious authentication and post-compromise activity. Because exploitation requires authentication, hardening credential security, enforcing MFA where applicable for administrative access paths, and rapidly investigating signs of credential theft can reduce risk until patching is completed. If no patch or compensating controls can be applied, discontinue use of the vulnerable service.

Remediation

Patch, then assume compromise.

Apply Microsoft's February 14, 2023 security updates for affected Microsoft Exchange Server versions. Organizations should ensure all supported Exchange installations are updated to the vendor-fixed builds for Exchange Server 2013 CU23, Exchange Server 2016 CU23, and Exchange Server 2019 CU11/CU12, and verify that no lagging or partially updated Exchange nodes remain in service.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationExchange Serverapplication
FAQ

Frequently asked questions

Is CVE-2023-21529 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 13, 2026.
Is there a public exploit for CVE-2023-21529?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2023-21529.
Is there a patch for CVE-2023-21529?
Apply Microsoft's February 14, 2023 security updates for affected Microsoft Exchange Server versions. Organizations should ensure all supported Exchange installations are updated to the vendor-fixed builds for Exchange Server 2013 CU23, Exchange Server 2016 CU23, and Exchange Server 2019 CU11/CU12, and verify that no lagging or partially updated Exchange nodes remain in service.
What products are affected by CVE-2023-21529?
Microsoft Corporation Exchange Server.
How severe is CVE-2023-21529?
CVE-2023-21529 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 59.3% (99th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence9Every report linking this CVE to a named adversary.
Associated malware8Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity14Community discussion across Reddit, Mastodon, and other social sources.