Skip to content
Server Security Center
KEVhigh7.8 Used in ransomware campaigns

CVE-2021-26857: Microsoft Exchange Server Remote Code Execution

Microsoft Exchange Server · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
7.8
high
EPSS (exploit probability, 30 days)
96%
higher than 99.8% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2021-26857 explained

CVE-2021-26857 is a remote code execution vulnerability in Microsoft Exchange Server, rooted in deserialization of untrusted data. It is part of the ProxyLogon exploit chain. CISA lists it as known exploited, including in ransomware campaigns, so unpatched Exchange servers face a serious risk of compromise.

Impact

Successful exploitation allows code execution on the Exchange server with high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. The CVSS vector lists a local attack vector, no privileges required and user interaction required. CISA judges it not automatable. Attackers are known to exploit it, including in ransomware campaigns, as part of the ProxyLogon chain.

Who is affected

The CVE record lists Microsoft Exchange Server 2010 Service Pack 3 before 14.03.0513.000. It also lists Exchange Server 2013 Service Pack 1 and Cumulative Updates 21, 22 and 23, fixed in 15.00.0847.064, 15.00.1395.012, 15.00.1473.006 and 15.00.1497.012. Exchange Server 2016 Cumulative Updates 10 to 16 are listed, fixed in builds from 15.01.1531.012 to 15.01.1979.008, one per update. Each listed product is affected below its fixed build. The page lists further affected products.

Written with AI from the data on this page and checked against it automatically.

Official description

Microsoft Exchange Server contains an unspecified vulnerability that allows for remote code execution. This vulnerability is part of the ProxyLogon exploit chain.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Exchange Server 2010 Service Pack 3
    Affected
    • < 14.03.0513.000
    Fixed in
    • 14.03.0513.000
  • Microsoft Exchange Server 2013 Cumulative Update 21x64
    Affected
    • < 15.00.1395.012
    Fixed in
    • 15.00.1395.012
  • Microsoft Exchange Server 2013 Cumulative Update 22x64
    Affected
    • < 15.00.1473.006
    Fixed in
    • 15.00.1473.006
  • Microsoft Exchange Server 2013 Cumulative Update 23x64
    Affected
    • < 15.00.1497.012
    Fixed in
    • 15.00.1497.012
  • Microsoft Exchange Server 2013 Service Pack 1x64
    Affected
    • < 15.00.0847.064
    Fixed in
    • 15.00.0847.064
  • Microsoft Exchange Server 2016 Cumulative Update 10x64
    Affected
    • < 15.01.1531.012
    Fixed in
    • 15.01.1531.012
  • Microsoft Exchange Server 2016 Cumulative Update 11x64
    Affected
    • < 15.01.1591.018
    Fixed in
    • 15.01.1591.018
  • Microsoft Exchange Server 2016 Cumulative Update 12x64
    Affected
    • < 15.01.1713.010
    Fixed in
    • 15.01.1713.010
  • Microsoft Exchange Server 2016 Cumulative Update 13x64
    Affected
    • < 15.01.1779.008
    Fixed in
    • 15.01.1779.008
  • Microsoft Exchange Server 2016 Cumulative Update 14x64
    Affected
    • < 15.01.1847.012
    Fixed in
    • 15.01.1847.012
Show 16 more products
  • Microsoft Exchange Server 2016 Cumulative Update 15x64
    Affected
    • < 15.01.1913.012
    Fixed in
    • 15.01.1913.012
  • Microsoft Exchange Server 2016 Cumulative Update 16x64
    Affected
    • < 15.01.1979.008
    Fixed in
    • 15.01.1979.008
  • Microsoft Exchange Server 2016 Cumulative Update 17x64
    Affected
    • < 15.01.2044.013
    Fixed in
    • 15.01.2044.013
  • Microsoft Exchange Server 2016 Cumulative Update 18x64
    Affected
    • < 15.01.2106.013
    Fixed in
    • 15.01.2106.013
  • Microsoft Exchange Server 2016 Cumulative Update 19x64
    Affected
    • < 15.01.2176.009
    Fixed in
    • 15.01.2176.009
  • Microsoft Exchange Server 2016 Cumulative Update 8x64
    Affected
    • < 15.01.1415.010
    Fixed in
    • 15.01.1415.010
  • Microsoft Exchange Server 2016 Cumulative Update 9x64
    Affected
    • < 15.01.1466.016
    Fixed in
    • 15.01.1466.016
  • Microsoft Exchange Server 2019x64
    Affected
    • < 15.02.0221.018
    Fixed in
    • 15.02.0221.018
  • Microsoft Exchange Server 2019 Cumulative Update 1x64
    Affected
    • < 15.01.1979.006
    Fixed in
    • 15.01.1979.006
  • Microsoft Exchange Server 2019 Cumulative Update 2x64
    Affected
    • < 15.02.0397.011
    Fixed in
    • 15.02.0397.011
  • Microsoft Exchange Server 2019 Cumulative Update 3x64
    Affected
    • < 15.02.0464.015
    Fixed in
    • 15.02.0464.015
  • Microsoft Exchange Server 2019 Cumulative Update 4x64
    Affected
    • < 15.02.0659.012
    Fixed in
    • 15.02.0659.012
  • Microsoft Exchange Server 2019 Cumulative Update 5x64
    Affected
    • < 15.02.0595.008
    Fixed in
    • 15.02.0595.008
  • Microsoft Exchange Server 2019 Cumulative Update 6x64
    Affected
    • < 15.02.0529.013
    Fixed in
    • 15.02.0529.013
  • Microsoft Exchange Server 2019 Cumulative Update 7x64
    Affected
    • < 15.02.0721.013
    Fixed in
    • 15.02.0721.013
  • Microsoft Exchange Server 2019 Cumulative Update 8x64
    Affected
    • < 15.02.0792.010
    Fixed in
    • 15.02.0792.010

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Exchange Server 2010 Service Pack 3: 14.03.0513.000
    • Microsoft Exchange Server 2013 Cumulative Update 21: 15.00.1395.012
    • Microsoft Exchange Server 2013 Cumulative Update 22: 15.00.1473.006
    • Microsoft Exchange Server 2013 Cumulative Update 23: 15.00.1497.012
    • Microsoft Exchange Server 2013 Service Pack 1: 15.00.0847.064
    • Microsoft Exchange Server 2016 Cumulative Update 10: 15.01.1531.012
    Fixed versions for 20 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26857
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify every Exchange server and its exact build number.
  2. Install the Microsoft security update for your Exchange version and cumulative update, reaching at least the fixed build listed in the CVE record.
  3. Follow the vendor advisory and CISA's required action: apply updates per vendor instructions.
  4. Restrict network exposure of Exchange servers to what is strictly needed.
  5. Check Exchange servers for signs of compromise, since this vulnerability is known to be exploited, including by ransomware operators.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-502 Deserialization of Untrusted Data

Questions about CVE-2021-26857

Is CVE-2021-26857 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and records known ransomware use. It is part of the ProxyLogon exploit chain.
Which build fixes my server?
It depends on your version and cumulative update. For example, Exchange Server 2010 Service Pack 3 is fixed in 14.03.0513.000 and Exchange Server 2016 Cumulative Update 16 in 15.01.1979.008. Check the affected products list for your exact update.
Is patching alone enough?
Patching closes the vulnerability but does not remove an existing compromise. Because attackers are known to exploit it, also check servers for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.