CVE-2026-85880: Windows ALPC local privilege escalation

Quick Answer

CVE-2026-85880 lets an attacker who can execute code in a low-privilege AppContainer escape that sandbox and gain Windows SYSTEM privileges. No additional user interaction is required. Match the host to the September CVRF updates below and investigate suspicious endpoint activity separately: Microsoft reports exploitation, but a KEV match does not prove compromise and patching cannot exclude earlier SYSTEM-level access.

Evidence check: CISA KEV catalog 2026.10.02 was checked on October 2. Vendor evidence and any unresolved fix limits are described below. Catalog inclusion confirms reported exploitation, not compromise of this deployment; verify current updates before production changes.

Context

Status At A Glance

Product scope	Microsoft — Windows
CVE	CVE-2026-85880
TechGeeks response tier	P0 — confirm an exact match and act now
CISA KEV added	2026-09-08
Vendor severity	Important
CVSS	7.8 (CVSS v3.1 base)
Ransomware field	Unknown — this is not the same as No; CISA has not marked the field Known.
Forensic-triage field	No in the current CISA field; organizations should still investigate when exposure or evidence warrants it.
CWE	CWE-122, CWE-908
Federal remediation date	2026-09-22 — applies to covered federal agencies; other organizations should set a risk-based deadline.

What Happened

Microsoft Windows Heap-Based Buffer Overflow Vulnerability. Microsoft Windows Advanced Local Procedure Call contains a heap-based buffer overflow vulnerability that allows an attacker to elevate privileges locally. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.

Affected Scope

Supported Windows client and server releases listed in the MSRC advisory; the vulnerable component is Advanced Local Procedure Call (ALPC).

Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.

Steps

What To Do Now

1. Confirm. Inventory every Windows asset and record its exact version, patch level, role, relevant configuration, and exposure.
2. Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
3. Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
4. Remediate. Install the applicable September 2026 or later Windows cumulative update and verify that the asset is on a fixed build listed by Microsoft.
5. Validate. Record the installed KB and Windows build after any required restart, compare them with Microsoft's CVE table, and check endpoint logging and the applications that run on the host. These checks do not reproduce the exploit or prove the absence of earlier compromise.
6. Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.

Fixed Releases And Mitigation

Investigation And Recovery

CISA lists this vulnerability as known exploited. On a matching vulnerable host, review endpoint telemetry for suspicious local privilege escalation to SYSTEM; installing the update does not establish that prior exploitation did not occur.

When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.

Notes

Exploitation Evidence

Vendor statement: Microsoft marked Exploited: Yes at original publication.

CISA statement: CVE-2026-85880 was added to KEV on 2026-09-08. The ransomware field is Unknown, and the forensic-triage field is No. These are separate signals.

Validation And Boundaries

This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.

Related TechGeeks Resources

• TechGeeks Security Notice Center
• All Security Notices
• What to Do When a Device Hits CISA KEV
• Router CVE Exposure, Version, and Mitigation Checklist
• IoT Firmware Update and End-of-Support Checklist
• Live Protect and Runtime Vulnerability Shielding

References

• Microsoft security advisory
• Microsoft security advisory
• CISA guidance
• CISA guidance
• NVD CVE record
• CISA source

Wrap-Up

Record whether CVE-2026-85880 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.

Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.