Skip to content
VulniPulse
High7.8Microsoft Server Exploited CISA KEV

High [CVE-2026-85880] Windows Advanced Local Procedure Call (ALPC) Elevation of Privilege Vulnerability

This high-severity Microsoft Server advisory covers CVE-2026-85880 affecting Windows Server 2012 (Server Core installation), Windows Server 2012 R2 (Server Core installation), Windows Server 2016 (Server Core installation).

CVE-2026-85880 Published Sep 8, 2026Updated by vendor Sep 8, 2026
Affected products & platforms
Microsoft ServerWindows Server
Open vendor advisory

Android app · Google Play

Monitor future Microsoft Server CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Heap-based buffer overflow in Windows ALPC allows an authorized attacker to elevate privileges locally.

Affected products named by the advisory: Windows Server 2012; Windows Server 2012 (Server Core installation); Windows Server 2012 R2; Windows Server 2012 R2 (Server Core installation); and 5 more.

Affected products named by the advisory: Windows Server 2016 (Server Core installation); Windows Server 2019 (Server Core installation); Windows Server 2022.

CISA Known Exploited Vulnerability

Listed:
Sep 8, 2026 · federal remediation due Sep 22, 2026
Required action:
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
Ransomware use:
Unknown

KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.

Affected versions
  • Windows 10 Version 1607 10.0.14393.0 before 10.0.14393.9512
  • Windows 10 Version 1809 10.0.17763.0 before 10.0.17763.9245
  • Windows 10 Version 21H2 10.0.19044.0 before 10.0.19044.7725
  • Windows 10 Version 22H2 10.0.19045.0 before 10.0.19045.7725
  • Windows Server 2012 6.2.9200.0 before 6.2.9200.26349
  • Windows Server 2012 (Server Core installation) 6.2.9200.0 before 6.2.9200.26349
  • Windows Server 2012 R2 6.3.9600.0 before 6.3.9600.23397
  • Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 before 6.3.9600.23397
  • Windows Server 2016 10.0.14393.0 before 10.0.14393.9512
  • Windows Server 2016 (Server Core installation) 10.0.14393.0 before 10.0.14393.9512
  • Windows Server 2019 10.0.17763.0 before 10.0.17763.9245
  • Windows Server 2019 (Server Core installation) 10.0.17763.0 before 10.0.17763.9245

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions
  • 10.0.14393.9512
  • 10.0.17763.9245
  • 10.0.19044.7725
  • 10.0.19045.7725
  • 6.2.9200.26349
  • 6.3.9600.23397
  • 10.0.20348.5622

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation

Upgrade to a fixed release: 10.0.14393.9512, 10.0.17763.9245, 10.0.19044.7725, 10.0.19045.7725, 6.2.9200.26349, 6.3.9600.23397. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.