Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged network authentication
-
ExploitReach vulnerable kernel interface
-
ExecutionSatisfy high-complexity trigger condition
-
ImpactBypass kernel security feature
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Strong authentication
|
| Exploitation Conditions | Exploitation requires the attacker to already possess low-level authenticated privileges (PR:L) and network reachability to the vulnerable Windows Kernel component (AV:N), and the high attack complexity (AC:H) indicates success depends on conditions outside the attacker's direct control - such as winning a timing/race window or a specific runtime state - rather than a single deterministic request. The description does not name the exact kernel security feature, protocol, or configuration setting involved, so the precise trigger cannot be pinned down from available data. Limiting factors that reduce realistic risk: the mandatory pre-existing authentication, the high complexity, and the fact that impact is confined to integrity (security-feature bypass) with no confidentiality or availability loss. |
| Impact | This is a moderate-severity (CVSS 5.3) security-feature-bypass in the Windows Kernel. The CVSS vector (AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N) shows a network-reachable flaw that nonetheless requires low-level privileges (PR:L) and high attack complexity (AC:H), with the only impact being to integrity (I:H) - specifically the ability to bypass a security feature; confidentiality and availability are unaffected. No EPSS score was provided, the CVE is not listed in CISA KEV, and no public proof-of-concept is referenced, so all exploitation signals point to no public exploit identified at time of analysis. The combination of high complexity plus required authentication substantially dampens real-world risk relative to the broad Windows attack surface: this is not a wormable, unauthenticated RCE but a conditions-dependent authentication-weakness (CWE-1390) that an already-authenticated attacker could use to defeat a protection boundary. Treat it as a standard Patch-Tuesday-tier fix to roll out on normal cadence rather than an emergency, while recognizing the ubiquity of the affected platform. Key caveat: no EPSS, SSVC, or POC data was supplied, so the exploitation-likelihood judgment rests only on the absence of KEV/POC signals and the AC:H/PR:L vector. |
| Exploit ScenarioDerived | An attacker who already holds low-privileged authenticated access reachable over the network engages a vulnerable Windows Kernel component and, by winning a race or satisfying specific runtime conditions implied by the high attack complexity, defeats a kernel security feature that should have blocked their action. Because impact is limited to integrity, the payoff is bypassing a protection boundary rather than reading data or crashing the host. No public exploit code is referenced, so exploitation would currently require original development. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A security-feature bypass in the Windows Kernel (CVE-2026-85939, CVSS 5.3) lets an authenticated attacker with only low-level privileges (PR:L per the CVSS vector) reach and subvert a kernel security control over the network, with the outcome limited to integrity impact - no loss of confidentiality or availability. Exploitation is not deterministic: the high attack-complexity rating (AC:H) indicates success depends on conditions outside the attacker's direct control, such as a race or timing window or a specific runtime state, and the affected kernel feature is not named in the available description. A vendor patch is available, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis; the risk is moderate and best addressed through prompt cumulative-update deployment across all supported Windows client and server branches listed in the advisory.
RemediationAI
Vendor-released patch: apply the Microsoft security update for CVE-2026-85939 from the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85939) so that affected systems are brought at or above the build levels shown in the advisory - for example 10.0.26100.9711 for Windows 11 24H2 and Windows Server 2025, 10.0.26200.9711 for Windows 11 25H2, 10.0.22631.7652 for Windows 11 23H2, 10.0.17763.9376 for Windows Server 2019 and Windows 10 1809, and 10.0.14393.9612 for Windows Server 2016 and Windows 10 1607 - deployed through Windows Update, WSUS, or your standard patch-management pipeline; because these are cumulative updates, installing the latest applicable servicing update for each branch is the correct action, and the exact build strings should be verified against MSRC as this CVE's source data shows a discrepancy for Windows 10 22H2. No specific workaround is published in the available data, so until patching completes use compensating controls whose trade-offs are understood: block or tightly ACL the network paths that expose the kernel's authenticated surface to untrusted segments (host firewall rules restricting SMB, RPC, and remote management to administrative subnets) at the cost of breaking legitimate remote file sharing and management, and enforce least privilege so that the population of low-privileged authenticated accounts able to reach these hosts is minimized, which reduces exposure but does not eliminate the bypass once an attacker holds such an account. Because the vulnerable kernel feature is unnamed, feature-specific hardening (for example enabling LSA protection or Credential Guard, tightening AppLocker/WDAC or attack surface reduction rules) may not cover the exact bypass path and should be treated as defense in depth rather than a fix, with the caveat that these controls can break legacy applications and management tooling. Given the AC:H, PR:L prerequisites and the absence of public exploit code or KEV-listed exploitation, this is a scheduled-patch priority rather than an emergency, but the affected servers should be patched on an accelerated timeline because kernel-level authentication bypasses are valuable to attackers who already have a foothold. If immediate patching is not feasible, monitor for anomalous authenticated activity touching kernel-exposed interfaces and audit for unexpected changes to security-relevant policy or configuration state, which would be consistent with the integrity-only impact of this bypass.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 16 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified as CWE-1390 (Weak Authentication) and resides in the Windows Kernel, the privileged core that arbitrates security boundaries such as token handling, privilege checks, and access enforcement for protected features. Because the vulnerable logic runs with kernel authority, an attacker who already holds an authenticated low-privileged session on or with network reach to the machine can attempt to bypass a kernel-level security feature rather than perform memory corruption - the assessed vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N reflects network reachability, mandatory pre-existing authentication, no user interaction, and integrity-only impact against the same security scope (security-feature bypass). The high complexity component signals the bypass is not a single reliable request but depends on a winning condition or particular system state, which constrains mass exploitation. Notably, the public description does not identify the exact kernel security feature, protocol, or configuration involved, so the precise trigger, the specific RPC/IOCTL/service surface used, and whether a specific Windows component (for example a token, credential, or policy-check feature) is implicated cannot be confirmed from the available data. No CPE strings were supplied, so affected-product identification relies on the vendor/EUVD build ranges rather than formal CPE enumeration, and the shadow vulnerability is tracked in the EU as EUVD-2026-99635 with the vendor advisory at MSRC as the authoritative source.
Know when Windows gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Network-reachable but needs authenticated low privileges (PR:L) and race/condition-dependent exploitation (AC:H); only a security-feature/integrity boundary is affected, so C:N and A:N.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Weak authentication in Windows Kernel allows an authorized attacker to bypass a security feature over a network.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
EUVD-2026-99635
GHSA-jvjp-4m6f-qvm9
NVD
CVE.org
EPSS
Exploit-DB