CVE-2022-41080: Microsoft Exchange Server Privilege Escalation
Microsoft Exchange Server · listed in the CISA catalog of actively exploited vulnerabilities since 2023-01-10.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 77%
- higher than 99.5% of all CVEs
- Added to CISA KEV
- 2023-01-10
- US federal due date 2023-01-31
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2022-41080 explained
CVE-2022-41080 is a privilege escalation vulnerability in Microsoft Exchange Server. It can be chained with CVE-2022-41082, which allows remote code execution. CISA lists it as known exploited, including in ransomware campaigns, so unpatched Exchange servers face a serious risk.
Impact
An attacker with low-privileged access can exploit the flaw over the network with low complexity and no user interaction. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA does not rate it as automatable. When chained with CVE-2022-41082, it can lead to remote code execution. CISA reports known use in ransomware campaigns.
Who is affected
The CVE record lists x64 builds of Exchange Server. 2013 Cumulative Update 23 is affected before 15.00.1497.044, fixed in that build. 2016 Cumulative Update 22 is affected before 15.01.2375.037, and 2016 Cumulative Update 23 before 15.01.2507.016. 2019 Cumulative Update 11 is affected before 15.02.0986.036, and 2019 Cumulative Update 12 before 15.02.1118.020. Each listed version contains the fix for its update.
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 privilege escalation. This vulnerability is chainable with CVE-2022-41082, which allows for remote code execution.
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 2013 Cumulative Update 23x64AffectedFixed in
- < 15.00.1497.044
- 15.00.1497.044
- Microsoft Exchange Server 2016 Cumulative Update 22x64AffectedFixed in
- < 15.01.2375.037
- 15.01.2375.037
- Microsoft Exchange Server 2016 Cumulative Update 23x64AffectedFixed in
- < 15.01.2507.016
- 15.01.2507.016
- Microsoft Exchange Server 2019 Cumulative Update 11x64AffectedFixed in
- < 15.02.0986.036
- 15.02.0986.036
- Microsoft Exchange Server 2019 Cumulative Update 12x64AffectedFixed in
- < 15.02.1118.020
- 15.02.1118.020
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Exchange Server 2013 Cumulative Update 23x64 |
|
|
| Microsoft Exchange Server 2016 Cumulative Update 22x64 |
|
|
| Microsoft Exchange Server 2016 Cumulative Update 23x64 |
|
|
| Microsoft Exchange Server 2019 Cumulative Update 11x64 |
|
|
| Microsoft Exchange Server 2019 Cumulative Update 12x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Exchange Server 2013 Cumulative Update 23: 15.00.1497.044
- Microsoft Exchange Server 2016 Cumulative Update 22: 15.01.2375.037
- Microsoft Exchange Server 2016 Cumulative Update 23: 15.01.2507.016
- Microsoft Exchange Server 2019 Cumulative Update 11: 15.02.0986.036
- Microsoft Exchange Server 2019 Cumulative Update 12: 15.02.1118.020
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41080
- CISA's deadline for US federal agencies: 2023-01-31 (passed) – a useful benchmark for everyone else, too.
What to do
- Identify all Exchange Server installations and their current build numbers.
- Install the Microsoft security update that brings each server to the fixed build listed for its Cumulative Update.
- Follow the Microsoft advisory and CISA's required action: apply updates per vendor instructions.
- Also make sure servers are protected against the chained flaw CVE-2022-41082.
- Limit internet exposure of Exchange services where possible.
- Check servers for signs of compromise, given known exploitation and ransomware use.
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
Questions about CVE-2022-41080
- Is CVE-2022-41080 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2023-01-10 and notes known ransomware use. The US federal due date was 2023-01-31.
- Why is it dangerous if it is only privilege escalation?
- It can be chained with CVE-2022-41082, which allows remote code execution. CISA rates the technical impact as total.
- Which build do I need?
- It depends on your Cumulative Update:
15.00.1497.044for 2013 CU23,15.01.2375.037for 2016 CU22,15.01.2507.016for 2016 CU23,15.02.0986.036for 2019 CU11 and15.02.1118.020for 2019 CU12.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
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.