Advisory

CVE-2026-85880: Microsoft Windows ALPC Heap-Based Buffer Overflow Enables Local Privilege Escalation

A heap-based buffer overflow in Microsoft Windows Advanced Local Procedure Call (ALPC) allows an authenticated local attacker to elevate privileges to a higher level, potentially gaining full system control. This vulnerability is listed in the CISA Known Exploited Vulnerabilities catalog, indicating confirmed real-world exploitation.

TL;DR: Apply Microsoft's patch immediately in accordance with vendor instructions and CISA BOD 26-04 guidance. If mitigations are unavailable, CISA directs agencies and operators to discontinue use of the affected product.

What Is the Flaw?

CVE-2026-85880 is a heap-based buffer overflow (CWE-122) combined with a use of uninitialized resource weakness (CWE-908) in the Microsoft Windows Advanced Local Procedure Call (ALPC) subsystem. ALPC is a core inter-process communication mechanism built into the Windows kernel, used extensively by system services and applications to exchange messages.

A heap-based buffer overflow occurs when a program writes more data into a buffer allocated on the heap than it was designed to hold. This overflows into adjacent memory regions, corrupting data structures in ways an attacker can manipulate to redirect program execution or alter security-sensitive state. In this case, the overflow resides in a privileged kernel-adjacent component, making the consequences severe.

The vulnerability was published to NVD on 2026-09-08 and carries a CVSS 3.1 score of 7.8 (HIGH) with the vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Breaking that vector down:

  • AV:L — Attack Vector is Local; the attacker must have local access to the machine.
  • AC:L — Attack Complexity is Low; no special conditions or race conditions are required.
  • PR:L — Privileged Required is Low; a standard, non-administrative user account is sufficient to trigger the flaw.
  • UI:N — No User Interaction is needed beyond the attacker's own actions.
  • C:H / I:H / A:H — Full impact on Confidentiality, Integrity, and Availability upon successful exploitation.

Who and What Is Affected?

The affected product is Microsoft Windows. Because ALPC is a foundational Windows subsystem, the exposure is broad across Windows environments. Organizations running Windows workstations, servers, or cloud-hosted Windows instances should treat this as a priority concern.

The attack requires the attacker to already hold a low-privileged, authenticated account on the target system. This makes the vulnerability particularly relevant in environments where:

  • Multiple users share systems (terminal servers, virtual desktop infrastructure).
  • Insider threat or compromised user credentials are a realistic risk.
  • Attackers have established an initial foothold via phishing, stolen credentials, or another vulnerability and are seeking to escalate within the environment.

Because the attack complexity is low and no user interaction is required, a threat actor who has cleared the initial access hurdle faces minimal technical barriers to exploitation.

Potential Impact

Successful exploitation allows a local attacker to elevate their privileges on the affected Windows system. Given that CVSS rates the impact on confidentiality, integrity, and availability all as High, the practical consequences can include:

  • Full system compromise: An attacker escalating from a low-privileged account could gain SYSTEM-level access, effectively owning the machine and all data on it.
  • Credential harvesting: With elevated privileges, an attacker can access credential stores, enabling lateral movement across the network.
  • Persistence and defense evasion: Administrative or SYSTEM-level access allows an attacker to disable security tooling, install persistent backdoors, and tamper with audit logs.
  • Data exfiltration or destruction: Elevated access removes most access control barriers to sensitive files, databases, and configurations.

CISA added this vulnerability to its Known Exploited Vulnerabilities (KEV) catalog on 2026-09-08, confirming that exploitation has been observed in the wild. This elevates urgency beyond theoretical risk.

What to Do Now

The required action, as specified by CISA, is clear:

  1. Apply mitigations in accordance with Microsoft's vendor instructions. Consult Microsoft's official security advisory for the patch applicable to your Windows version and apply it promptly. Follow CISA's BOD 26-04 (Prioritizing Security Updates Based on Risk) patching timelines, which apply to federal agencies and serve as strong guidance for all organizations.
  2. Conduct forensic triage where warranted. CISA's KEV entry references "Forensics Triage Requirements." Organizations in sensitive sectors should consult CISA's guidance to determine whether forensic review of potentially exposed systems is appropriate.
  3. Cloud-hosted Windows environments. Follow the applicable BOD 26-04 guidance for cloud services. Responsibility for patching may be shared between the cloud provider and the customer depending on the service model; verify patch status with your provider if you do not manage the OS layer directly.
  4. Discontinue use if mitigations are unavailable. If a patch or mitigation cannot be applied, CISA directs that use of the affected product be discontinued until it can be secured.
  5. Prioritize internet-exposed and high-value systems. While the attack vector is local, systems accessible via RDP, VDI, or other remote access mechanisms effectively lower the bar for a threat actor who can authenticate remotely before exploiting locally.
  6. Review least-privilege posture. Ensure users operate with the minimum privileges necessary. While this does not eliminate the vulnerability, it reduces the blast radius of any exploitation.

How External Testing Helps Surface Exposure

Privilege escalation vulnerabilities like CVE-2026-85880 sit one step beyond the network perimeter, but external security testing still plays a meaningful role in managing the risk:

  • Patch verification: Point-in-time vulnerability scanning can confirm whether a given Windows host has received the relevant patch, helping prioritize remediation queues and validate that patch deployment has been effective.
  • Attack surface mapping: Identifying which Windows systems expose remote access services (such as RDP or exposed management interfaces) helps determine which hosts, if compromised via initial access, would become immediate targets for local privilege escalation.
  • Configuration assessment: Scanning can surface misconfigurations — such as overly permissive local accounts or exposed administrative shares — that increase the ease with which an attacker could weaponize a local privilege escalation flaw.
  • Prioritization support: Not all Windows systems carry equal risk. External testing data combined with asset criticality ratings helps security teams allocate patching effort where it matters most.

Because exploitation requires local access, internal vulnerability assessments and endpoint detection tooling complement external scanning and together provide a more complete picture of organizational exposure.

Sources & further reading: NVD CVE-2026-85880 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: msrc.microsoft.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Does an attacker need physical access to the machine to exploit CVE-2026-85880?

No. The CVSS attack vector is Local (AV:L), which means the attacker needs a local account on the system, not necessarily physical presence. An attacker who has established remote access — for example, through a compromised user account connecting via Remote Desktop — can satisfy this requirement without being physically present at the device.

Is this vulnerability being actively exploited?

Yes. CISA added CVE-2026-85880 to its Known Exploited Vulnerabilities catalog on 2026-09-08, which confirms that active exploitation has been observed. Organizations should treat patching as urgent rather than routine.

What is ALPC and why does a vulnerability there matter so much?

Advanced Local Procedure Call (ALPC) is a core inter-process communication mechanism built into the Windows operating system. It is used by a wide range of system services and privileged components. A vulnerability in ALPC is significant because successfully exploiting it can interact with highly privileged code paths, making privilege escalation to SYSTEM-level access realistic.

What if we cannot patch immediately — are there interim mitigations?

CISA's required action directs organizations to follow Microsoft's vendor instructions for mitigations and to reference BOD 26-04 guidance. If no mitigations are available and patching cannot be completed, CISA instructs that use of the affected product be discontinued. Organizations should consult Microsoft's official advisory for any available workarounds and assess the feasibility of isolating at-risk systems while patching is arranged.