CVE-2026-85880: Microsoft Windows Heap-Based Buffer Overflow
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2026-09-08.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 0.4%
- higher than 33.5% of all CVEs
- Added to CISA KEV
- 2026-09-08
- US federal due date 2026-09-22
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2026-85880 explained
CVE-2026-85880 is a heap-based buffer overflow in Windows ALPC that lets an authorized local attacker elevate privileges. It affects several Windows 10 and Windows Server releases. CISA lists it as known exploited, so affected systems should be updated with priority.
Impact
An attacker who already has low-privileged local access can elevate privileges without any user interaction. A successful attack gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. Exploitation is not automatable at scale and requires local access. Attackers are known to use this vulnerability. Whether it is used in ransomware campaigns is unknown.
Who is affected
Affected: Windows 10 Version 1607 and Windows Server 2016 (including Server Core) before 10.0.14393.9512; Windows 10 Version 1809 and Windows Server 2019 (including Server Core) before 10.0.17763.9245; Windows 10 Version 21H2 before 10.0.19044.7725; Windows 10 Version 22H2 before 10.0.19045.7725; Windows Server 2012 (including Server Core) before 6.2.9200.26349; Windows Server 2012 R2 (including Server Core) before 6.3.9600.23398. Each listed fixed version resolves the issue for its product.
Written with AI from the data on this page and checked against it automatically.
Official description
Heap-based buffer overflow in Windows ALPC allows an authorized attacker to elevate privileges locally.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 160732-bit, x64AffectedFixed in
- < 10.0.14393.9512
- 10.0.14393.9512
- Microsoft Windows 10 Version 180932-bit, x64AffectedFixed in
- < 10.0.17763.9245
- 10.0.17763.9245
- Microsoft Windows 10 Version 21H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19044.7725
- 10.0.19044.7725
- Microsoft Windows 10 Version 22H232-bit, ARM64, x64AffectedFixed in
- < 10.0.19045.7725
- 10.0.19045.7725
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.26349
- 6.2.9200.26349
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.26349
- 6.2.9200.26349
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.23398
- 6.3.9600.23398
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.23398
- 6.3.9600.23398
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.9512
- 10.0.14393.9512
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.9512
- 10.0.14393.9512
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.9245
- 10.0.17763.9245
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.9245
- 10.0.17763.9245
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.5622
- 10.0.20348.5622
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 160732-bit, x64 |
|
|
| Microsoft Windows 10 Version 180932-bit, x64 |
|
|
| Microsoft Windows 10 Version 21H232-bit, ARM64, x64 |
|
|
| Microsoft Windows 10 Version 22H232-bit, ARM64, 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 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1607: 10.0.14393.9512
- Microsoft Windows 10 Version 1809: 10.0.17763.9245
- Microsoft Windows 10 Version 21H2: 10.0.19044.7725
- Microsoft Windows 10 Version 22H2: 10.0.19045.7725
- Microsoft Windows Server 2012: 6.2.9200.26349
- Microsoft Windows Server 2012 (Server Core installation): 6.2.9200.26349
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85880
- CISA's deadline for US federal agencies: 2026-09-22 (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 version.
- Prioritize systems where many users have local or remote logon access, such as shared servers and terminal hosts.
- Follow the Microsoft advisory and CISA's required action, including BOD 26-04 guidance, before the federal due date of 2026-09-22.
- Limit local and interactive logon rights to trusted accounts to reduce who can attempt privilege escalation.
- Check affected systems for signs of compromise, such as unexpected privileged accounts or processes.
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-122 Heap-based Buffer Overflow, CWE-908 Use of Uninitialized Resource
Questions about CVE-2026-85880
- Can this be exploited remotely?
- No. The attack vector is local. An attacker needs an existing low-privileged account or code running on the system, then can elevate privileges without user interaction.
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-85880 to its Known Exploited Vulnerabilities catalog on 2026-09-08, with a US federal due date of 2026-09-22. Known ransomware use is listed as unknown.
- Which build fixes Windows Server 2019?
- Windows Server 2019, including Server Core installations, is fixed in
10.0.17763.9245. Earlier builds are affected.
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-21. Always confirm with the vendor's or distribution's advisory before patching.