CVE-2022-41033: Microsoft Windows COM+ Event System Service Privilege Escalation
Microsoft Windows COM+ Event System Service · listed in the CISA catalog of actively exploited vulnerabilities since 2022-10-11.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 1.9%
- higher than 80% of all CVEs
- Added to CISA KEV
- 2022-10-11
- US federal due date 2022-11-01
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2022-41033 explained
CVE-2022-41033 is a privilege escalation vulnerability in the Microsoft Windows COM+ Event System Service, classified as a type confusion weakness (CWE-843). It affects Windows 10, Windows 11 and Windows Server releases. CISA lists it as known to be exploited by attackers, which makes patching a priority.
Impact
An attacker who already has low-privileged local access can escalate privileges without any user interaction. Successful exploitation has high impact on confidentiality, integrity and availability. CISA rates the technical impact as total, meaning total control of the affected component. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to use this vulnerability; whether it is used in ransomware campaigns is unknown.
Who is affected
Affected builds include Windows 10 Version 1809, Windows Server 2019 and its Server Core installation before 10.0.17763.3532, Windows 10 Version 21H1 before 10.0.19043.2130, 20H2 before 10.0.19042.2130, 21H2 before 10.0.19044.2130, Windows Server 2022 before 10.0.20348.1129, Windows 11 version 21H2 before 10.0.22000.1098, 22H2 before 10.0.22621.674, Windows 10 Version 1507 before 10.0.10240.19507, and Windows 10 Version 1607 and Windows Server 2016 before 10.0.14393.5427. The listed builds contain the fix. Further products are listed on this page.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft Windows COM+ Event System Service contains an unspecified vulnerability that allows for privilege escalation.
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 Windows 10 Version 180932-bit, x64, ARM64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.3532
- 10.0.17763.3532
- Microsoft Windows 10 Version 21H1x64, ARM64, 32-bitAffectedFixed in
- < 10.0.19043.2130
- 10.0.19043.2130
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.1129
- 10.0.20348.1129
- Microsoft Windows 10 Version 20H232-bit, ARM64AffectedFixed in
- < 10.0.19042.2130
- 10.0.19042.2130
- Microsoft Windows 11 version 21H2x64, ARM64AffectedFixed in
- < 10.0.22000.1098
- 10.0.22000.1098
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.2130
- 10.0.19044.2130
- Microsoft Windows 11 version 22H2ARM64, x64AffectedFixed in
- < 10.0.22621.674
- 10.0.22621.674
- Microsoft Windows 10 Version 150732-bit, x64AffectedFixed in
- < 10.0.10240.19507
- 10.0.10240.19507
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 180932-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows 10 Version 21H1x64, ARM64, 32-bit |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows 10 Version 20H232-bit, ARM64 |
|
|
| Microsoft Windows 11 version 21H2x64, ARM64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 11 version 22H2ARM64, x64 |
|
|
| Microsoft Windows 10 Version 150732-bit, x64 |
|
|
Show 14 more products
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.5427
- 10.0.14393.5427
- Microsoft Windows 732-bitAffectedFixed in
- < 6.1.7601.26174
- 6.1.7601.26174
- Microsoft Windows 7 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26174
- 6.1.7601.26174
- Microsoft Windows 8.132-bit, x64, ARM64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
- Microsoft Windows Server 2008 Service Pack 232-bit, x64AffectedFixed in
- < 6.0.6003.21721
- 6.0.6003.21721
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64AffectedFixed in
- < 6.0.6003.21721
- 6.0.6003.21721
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.26174
- 6.1.7601.26174
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.26174
- 6.1.7601.26174
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.23920
- 6.2.9200.23920
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.23920
- 6.2.9200.23920
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.20625
- 6.3.9600.20625
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows 732-bit |
|
|
| Microsoft Windows 7 Service Pack 1x64 |
|
|
| Microsoft Windows 8.132-bit, x64, ARM64 |
|
|
| Microsoft Windows Server 2008 Service Pack 232-bit, x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)32-bit, x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1809: 10.0.17763.3532
- Microsoft Windows Server 2019: 10.0.17763.3532
- Microsoft Windows Server 2019 (Server Core installation): 10.0.17763.3532
- Microsoft Windows 10 Version 21H1: 10.0.19043.2130
- Microsoft Windows Server 2022: 10.0.20348.1129
- Microsoft Windows 10 Version 20H2: 10.0.19042.2130
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2022-41033
- CISA's deadline for US federal agencies: 2022-11-01 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the Microsoft security update that brings each system to the fixed build listed for its Windows release, for example
10.0.17763.3532or10.0.22621.674. - Follow the vendor advisory to confirm the correct update for every affected product, including those listed further on this page.
- Prioritize systems where many users have local or remote logon access, since the attack needs local low-privileged access.
- Limit local logon rights and remove unnecessary user accounts to reduce who can reach the vulnerable service.
- Check systems for signs of compromise, such as unexpected privileged accounts or processes, given known exploitation.
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-843 Access of Resource Using Incompatible Type ('Type Confusion')
Questions about CVE-2022-41033
- Is CVE-2022-41033 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-10-11. Its required action is to apply updates per vendor instructions. US federal agencies had a due date of 2022-11-01. Known ransomware use is listed as unknown.
- Can it be exploited remotely without credentials?
- No. The attack vector is local and low privileges are required. An attacker must already be able to run code on the system with a standard account. No user interaction is needed.
- How do I know if a system is fixed?
- Compare the Windows build number with the fixed build for that release in the CVE record, such as
10.0.20348.1129for Windows Server 2022 or10.0.22000.1098for Windows 11 version 21H2. Builds at or above that number contain the fix.
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.