Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticated local code execution
-
DeliveryTrigger use-after-free in NTFS driver
-
ExploitCorrupt and reclaim freed kernel object
-
ExecutionExecute code in kernel context
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires authenticated local access to the Windows host and the ability to run code that drives NTFS filesystem operations to trigger the use-after-free in the NTFS driver (AV:L, UI:N). Per Microsoft's vector the attacker must already hold high privileges (PR:H), though this is atypically high for an NTFS EoP and should be confirmed. Exploitation is limited to the specific patched Windows 11 (24H2/25H2/26H1) and Windows Server 2025 build ranges listed in the EUVD data; there is no remote or network-based path, and no default-configuration remote exposure. The practical limiting factors are the need for a valid local account/foothold and the local-only vector, which prevent remote or automatable mass exploitation (SSVC Automatable=no). |
| Impact | Signals are largely consistent and point to a moderate, not top-tier, priority. The CVSS 3.1 base score of 6.7 reflects a local attack vector (AV:L), low complexity (AC:L), and - per Microsoft - high privileges required (PR:H) with no user interaction, yielding full confidentiality/integrity/availability impact (C:H/I:H/A:H) on an unchanged scope. CISA's SSVC framework reinforces this: Exploitation=none (no known in-the-wild activity), Automatable=no (local-only, cannot be mass-scanned/wormed), but Technical Impact=total (consistent with a kernel use-after-free granting SYSTEM). There is no CISA KEV listing and no public POC referenced, so this is not confirmed as actively exploited. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. One notable tension: Microsoft sets PR:H, which is unusually high for an NTFS local privilege-escalation UAF (such flaws are frequently exploitable by any low-privileged authenticated user, i.e. PR:L); if PR is in fact lower, real-world risk would be higher than the 6.7 suggests - verify the exact privilege prerequisite with Microsoft. Also note the 'Denial Of Service' tag conflicts with the description, which states privilege elevation, not availability loss - treat the DoS characterization with caution. |
| Exploit ScenarioDerived | An attacker who already has a valid local account on a Windows host runs a crafted program that manipulates NTFS operations to trigger the use-after-free in the filesystem driver, corrupting kernel memory to execute code at SYSTEM level. No user interaction is required and the attack is entirely local. No public exploit identified at time of analysis, so a working exploit would need to be developed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Windows NTFS lets an authenticated attacker with local access to an affected Windows host trigger a use-after-free in the NTFS file system driver, which can lead to high-integrity code execution in kernel context and elevation to SYSTEM. The issue affects specific Windows 11 24H2, 25H2, and 26H1 builds and Windows Server 2025 (including Server Core) below the fixed builds listed in the Microsoft advisory. CVSS base score is 6.7, it is not in CISA KEV, and no public exploit identified at time of analysis; SSVC records exploitation as none and automatable as no, keeping the practical risk moderate and requiring a local foothold.
RemediationAI
Apply the vendor-released patch: Microsoft's update for CVE-2026-83706 fixes Windows Server 2025 build 10.0.26100.33438, Windows 11 version 24H2 build 10.0.26100.9445, Windows 11 version 25H2 build 10.0.26200.9445, and Windows 11 version 26H1 build 10.0.28000.2954; see https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83706 for the applicable KB and installation guidance. Because exploitation requires authenticated local access and code execution on the host, there is no network or perimeter workaround, so compensating controls should focus on reducing local attack surface: enforce least privilege so users cannot run untrusted code, restrict interactive logon and local administrator rights to necessary personnel, and monitor for unusual NTFS driver activity or kernel memory corruption crashes; these controls can disrupt legitimate administrative workflows and do not eliminate the flaw, so patching remains the primary remediation. No public exploit is identified, and SSVC indicates exploitation is none and automatable is no, so emergency out-of-band action is not warranted, but standard patch cycles should be prioritized for systems matching the affected builds.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 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 vulnerability is a CWE-416 use-after-free in the Windows NTFS kernel-mode file system driver, a memory-safety flaw that can corrupt kernel memory when an attacker triggers filesystem operations that cause a freed NTFS structure to be reused. The CVSS:3.1 vector AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H provided by the vendor indicates a local, non-user-interactive attack requiring high privileges, while the independent assessment uses PR:L but agrees on local-only access, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact; both require an authenticated local account, and there is no remote or network attack path. EUVD build ranges map the affected products to Windows 11 24H2/25H2/26H1 and Windows Server 2025, and no CPE strings were supplied in the intelligence feed. The SSVC assessment rates exploitation as none, automatable as no, and technical impact as total, and the tags 'Denial Of Service', 'Use After Free', and 'Memory Corruption' reflect the possibility of crashes or memory corruption in addition to privilege escalation; exploitation requires the attacker to already execute code locally to drive NTFS operations.
Know when the next one hits your stack
- 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:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Local UAF in NTFS triggerable by a logged-in user with code execution, so AV:L/AC:L/PR:L (NTFS EoP typically needs only low privilege; vendor's PR:H would lower the score to 6.7); kernel compromise yields C/I/A:H.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows NTFS allows an authorized attacker to elevate privileges locally.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-99338
GHSA-gg5q-fqhf-h2qh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB