CVE-2023-21529Microsoft Exchange Server Deserialization of Untrusted Data Vulnerability
CVE-2023-21529 is a deserialization of untrusted data in Microsoft Exchange Server, rated high (8.8 on CVSS 3.1).
Why this priority: Exploited in the wild: listed in CISA's KEV catalog.
Published · Updated · NVD status: Analyzed
What it is
Serialized objects from outside are turned back into live objects, which a crafted payload can abuse to run code.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker turn crafted data into code execution inside the receiving service.
Is it being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 2026-04-13: it is being exploited in the wild. CISA links it to ransomware campaigns. EPSS estimates a 59% chance of exploitation activity in the next 30 days, higher than 99% of scored CVEs.
What to do
- Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-04-27.
- Apply the update for your edition of Microsoft Exchange Server. Fixed builds: Microsoft Exchange Server 2013 Cumulative Update 23: 15.00.1497.047; Microsoft Exchange Server 2016 Cumulative Update 23: 15.01.2507.021; Microsoft Exchange Server 2019 Cumulative Update 11: 15.02.0986.041; Microsoft Exchange Server 2019 Cumulative Update 12: 15.02.1118.025. The patch notes are linked below.
- Until it is patched, review who holds accounts that can reach it.
- Check exposed instances for signs of compromise, not only for the version.
Description from NVD
Microsoft Exchange Server Remote Code Execution Vulnerability
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- APIs, queues and caches that accept serialized objects. The flaw sits between a message producer and the service that deserializes it.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between a message producer and the service that deserializes it. An attacker who crosses it can turn crafted data into code execution inside the receiving service.
Questions to answer about your own systems
- Where does Microsoft Exchange Server run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.