Windows Servicing Stack CVE-2026-85365

Requires the attacker to already have authenticated, low-privileged local access to the Windows host (PR:L, AV:L) - this is not remotely reachable and needs no user interaction. The flaw resides in the Servicing Stack Updates (SSU) component, which processes Windows update servicing operations, so exploitation exercises that update-servicing code path. Exploitation is LIMITED by HIGH attack complexity (AC:H): success depends on conditions the attacker cannot fully control, consistent with a race condition or precise heap-layout requirement rather than a deterministic trigger. Only versions below the fixed build in each Windows edition (e.g., Windows 11 24H2 before 10.0.26100.9711, Windows Server 2025 before 10.0.26100.33650, Windows Server 2012 R2 before 6.3.9600.23470) are affected; patched builds remove the condition.

This is a genuine but moderate-priority elevation-of-privilege flaw rather than an urgent fire-drill. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0 HIGH) describes a local attack requiring an already-authenticated low-privileged user and, critically, a HIGH attack complexity - meaning the attacker must win a race or satisfy conditions outside their control, which materially dampens reliability. Multiple non-CVSS signals agree that this is NOT a widespread-exploitation concern: it is NOT listed in CISA KEV, no public POC is referenced, and the CISA SSVC decision framework rates Exploitation as 'none' and Automatable as 'no'. The only amplifying signal is SSVC Technical Impact 'total', which is consistent with the C:H/I:H/A:H full-system-compromise impact once the overflow succeeds. Signals are therefore internally consistent (no CVSS-vs-description conflict here: description says 'locally' and 'authorized attacker', matching AV:L/PR:L). Net: a reliable, high-impact local privilege escalation primitive that is valuable to an attacker who already has a foothold, but low likelihood of mass or automated exploitation given AC:H and the absence of any exploitation evidence.

An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing, a compromised service account, or a separate initial-access bug) triggers the heap-based buffer overflow in the Servicing Stack Updates component to corrupt heap memory and gain SYSTEM-level privileges. No public exploit identified at time of analysis, and the HIGH attack complexity means success likely depends on winning a race condition or precise heap grooming rather than a one-shot deterministic exploit.