Skip to main content

Windows NTFS CVE-2026-83585

| EUVDEUVD-2026-99924 HIGH
Use of Externally-Controlled Format String (CWE-134)
2026-10-13 secure@microsoft.com GHSA-gx59-32g8-8fj7
7.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local account
  2. Exploit
    Supply externally-controlled format string to NTFS
  3. Execution
    Trigger CWE-134 memory corruption
  4. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Format string safety
Exploitation Conditions

Exploitation requires the attacker to already possess local access with at least low-level privileges (CVSS PR:L) on an affected Windows system - i.e., the ability to execute a crafted local process that passes attacker-controlled format-string input into the vulnerable Windows NTFS code path. No user interaction is required (UI:N) and no special or non-default configuration is indicated; the vulnerable NTFS driver is part of default Windows installations across the listed Windows 10/11, Server 2012 through Server 2025 builds. The principal limiting factor is the need for a pre-existing authenticated local foothold: the flaw is not remotely reachable (AV:L) and SSVC marks it non-automatable, so it serves as a privilege-escalation stage rather than an initial-access or self-spreading vector.

Impact

This is a local elevation-of-privilege flaw in Windows NTFS (CWE-134, externally-controlled format string). The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) indicates a local attack vector with low complexity requiring low privileges and no user interaction, yielding total confidentiality, integrity and availability impact - consistent with full SYSTEM compromise from a low-privileged foothold. The signals are internally consistent but point to a prioritize-but-not-emergency posture: CISA's SSVC decision shows Exploitation=none, Automatable=no, and Technical Impact=total, meaning high damage potential if exploited but no observed exploitation and no automatability (expected for a local EoP that cannot self-propagate). There is no KEV listing, no POC reference, and no EPSS score in the supplied data - so exploitation probability cannot be quantified and absence of EPSS/KEV/POC should not be read as proof of safety. Because PR:L requires an attacker to already hold a valid low-privileged local account or code-execution foothold, real-world risk is gated on prior access; this is a classic second-stage privilege-escalation primitive rather than an initial-access or wormable threat. Net: a genuine patch-priority item given ubiquitous Windows footprint and total technical impact, but not an immediate drop-everything emergency absent evidence of active exploitation.

Exploit ScenarioDerived

An attacker who has already gained a low-privileged foothold on a Windows host (e.g., via phishing, a standard user account, or a prior exploit) runs a crafted local process that supplies attacker-controlled format-string data to a vulnerable NTFS code path, corrupting memory or manipulating formatted output to escalate to SYSTEM. No user interaction is required and attack complexity is low once local access exists. No public exploit identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in Windows NTFS lets an attacker who already holds low-privileged local access on an affected Windows installation feed attacker-controlled input into a format-string handling path in the file system driver, resulting in elevated privileges with full impact to confidentiality, integrity and availability (CVSS 7.8). The flaw is not remotely reachable and no public exploit has been identified at time of analysis; CISA's SSVC assessment rates exploitation as 'none' and the flaw as non-automatable, so it functions as a post-compromise privilege-escalation stage rather than an initial-access or self-propagating vector. Microsoft has released fixed builds for the affected Windows 10, Windows 11 and Windows Server versions.

RemediationAI

Vendor-released patch: Microsoft has published fixed builds covering every affected branch, so remediation is to apply the current cumulative security update rather than a standalone NTFS hotfix - specifically Windows 11 24H2 to 10.0.26100.9711, 25H2 to 10.0.26200.9711, 26H2 to 10.0.26300.9711, 26H1 to 10.0.28000.3231 and 23H2 to 10.0.22631.7652; Windows 10 21H2/22H2 to 10.0.19044.7807, 1809 to 10.0.17763.9376 and 1607 to 10.0.14393.9612; and Windows Server 2025 to 10.0.26100.33650, Server 2022 to 10.0.20348.5761, Server 2019 to 10.0.17763.9376, Server 2016 to 10.0.14393.9612, Server 2012 R2 to 6.3.9600.23470 and Server 2012 to 6.2.9200.26434 - coordinating deployment through the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83585 and your normal patch-ring process, with priority on multi-user systems such as terminal servers, VDI hosts and jump boxes where a low-privileged local foothold is easiest to obtain and hardest to contain. No configuration workaround removes the defect itself, so where patching must be deferred the pragmatic mitigations are to reduce the population of accounts and processes that can execute arbitrary local code on sensitive hosts: enforce least privilege and remove unnecessary local interactive logon rights, and use WDAC or AppLocker in allow-list mode to block unsigned or unapproved binaries on high-value servers - accepting the operational cost that legitimate in-house tools must be signed and explicitly whitelisted beforehand. Because exploitation is local and requires an existing foothold (SSVC: not automatable, exploitation 'none'), detection effort is better spent on post-exploitation behaviour than on network signatures: alert on unexpected processes spawning from services or low-integrity contexts, on suspicious token or privilege changes, and on crash telemetry from ntfs.sys or other kernel drivers, which can indicate a failed format-string attempt. Nothing in the available data points to a remote or self-propagating vector, so perimeter and email controls need no CVE-specific change.

Affected VersionsENISA

Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2022 10.0.20348.0 <10.0.20348.5761

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 20 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 root cause is CWE-134, Use of Externally-Controlled Format String, in the Windows NTFS file system driver (ntfs.sys) and related NTFS code paths shipped in default Windows installations. A format-string defect occurs when a buffer containing attacker-influenced data is passed directly as the format argument to a printf-family routine rather than as data to a fixed format string; the injected conversion specifiers are then interpreted by the kernel routine. Read specifiers such as %x or %s can disclose stack or memory contents - consistent with the 'Information Disclosure' tag attached to this issue - while the %n specifier allows writes to attacker-chosen addresses, which in kernel mode is the classic path to memory corruption and SYSTEM-level code execution. This CVE's CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H vector and the SSVC 'Technical Impact: total' rating indicate that a successful exploit yields complete loss of confidentiality, integrity and availability on the host. Because the vector is AV:L with PR:L, the vulnerable code path is reachable only from a local process already running under a low-privileged, authenticated context; there is no network or remote attack surface, no user interaction requirement (UI:N), and scope remains unchanged (S:U), meaning the compromise is confined to the affected system's security authority rather than crossing a trust boundary such as a hypervisor or container.

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

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local-only NTFS flaw requiring a low-privileged account (AV:L, PR:L) with no user interaction and reliable triggering (AC:L), yielding full SYSTEM compromise (C/I/A:H).

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.8

DescriptionCVE.org

Use of externally-controlled format string in Windows NTFS allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A high-severity local privilege escalation vulnerability in the Windows NTFS file system driver allows an attacker with existing low-privileged access to gain elevated privileges on affected Windows 10, Windows 11, and Windows Server systems, compromising confidentiality, integrity, and availability. This post-compromise escalation path increases the risk of full host takeover, lateral movement, and data loss following an initial foothold, making timely patching critical to reducing organizational exposure. Microsoft has released fixed builds, and while no public exploit has been identified, leadership should ensure remediation is prioritized to protect against insider threats and advanced attackers.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Ubiquitous
Windows NTFS is present on essentially all Windows desktop and server installs
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy