Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local access
-
DeliveryPresent crafted exFAT volume for parsing
-
ExploitTrigger heap buffer overflow in exFAT driver
-
ExecutionCorrupt kernel heap structures
-
ImpactElevate to SYSTEM
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires local, authenticated low-privilege access to an affected Windows host (CVSS PR:L), after which the attacker must get the vulnerable exFAT driver to parse attacker-controlled exFAT file system metadata - in practice by having a crafted exFAT-formatted volume (e.g., a malicious USB device, mounted disk image, or VHD) processed by the system. CVSS UI:N indicates no interaction by a separate victim user is modeled. Limiting factors: no remote network vector (AV:L), the attacker needs an existing foothold/account on the machine, and the target must process the malicious exFAT volume; environments that block removable media or restrict mounting of untrusted images materially reduce exposure. Applies broadly across supported Windows 10, Windows 11 (23H2-26H2), and Windows Server 2012 through 2025 builds below the patched versions listed in EUVD. |
| Impact | This is a credible, patch-now-class local privilege escalation rather than a hype-driven high-CVSS item. The CVSS:3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) is internally consistent with the description of a heap-based buffer overflow (CWE-122) in the Windows exFAT file system allowing an authorized attacker to elevate privileges locally. All three real-world acceleration signals are, however, ABSENT from the input: there is no EPSS score, no CISA KEV listing, and no POC indicator - therefore exploitation status is 'no public exploit identified at time of analysis'. There is no SSVC decision record supplied. The attack vector is Local with Low complexity and no user interaction, but it requires existing low-privilege authenticated access (PR:L), which bounds the blast radius to post-compromise escalation (e.g., chaining after a phishing foothold or a low-priv service). The signals are not conflicting - they consistently point to a serious-but-not-remote local EoP. The dominant risk driver is the enormous install base (Windows), not exploitation evidence. Treat as high priority for patch prioritization on multi-user, kiosk, and removable-media-exposed hosts, while noting the local-access prerequisite lowers mass-exploitation likelihood absent a public exploit. |
| Exploit ScenarioDerived | A low-privileged but authenticated attacker on a Windows host (or malware running in a restricted context) supplies a maliciously crafted exFAT volume - for example a specially formatted USB device or disk image - whose metadata triggers a heap-based buffer overflow when the exFAT driver parses it. Successful corruption of kernel heap structures lets the attacker elevate to SYSTEM. No public exploit code is identified at time of analysis, and CVSS AC:L suggests the overflow is reliably reachable once the attacker can get the volume parsed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
A heap-based buffer overflow (CWE-122) in the Windows exFAT file system driver allows a local, authenticated low-privilege attacker to elevate privileges to kernel/SYSTEM level, rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). To trigger it, the attacker must first hold an account on the host and then cause the vulnerable driver to parse attacker-controlled exFAT metadata - realistically a crafted exFAT-formatted USB device, disk image or VHD - so systems that block removable media or untrusted image mounting are materially less exposed. Affected hosts include Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2/26H1) and Windows Server 2012 through 2025 (including Server Core) at builds below the patched thresholds published in Microsoft's advisory. There is no CISA KEV listing and no public exploit identified at time of analysis, and vendor patches are available, making this a credible patch-now local privilege-escalation item rather than a remotely exploitable or actively exploited threat.
RemediationAI
Patch status: vendor-released patches are available, with fixed build thresholds of 6.2.9200.26434 (Server 2012), 6.3.9600.23470 (Server 2012 R2), 10.0.14393.9612 (Windows 10 1607 / Server 2016), 10.0.17763.9376 (Windows 10 1809 / Server 2019), 10.0.19044.7807 (Windows 10 21H2 and 22H2), 10.0.20348.5761 (Server 2022), 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.9711 (Windows 11 24H2), 10.0.26100.33650 (Server 2025), 10.0.26200.9711 (Windows 11 25H2), 10.0.26300.9711 (Windows 11 26H2) and 10.0.28000.3231 (Windows 11 26H1); apply the matching Microsoft updates via Windows Update, WSUS or the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85822 and confirm the reported build meets or exceeds the threshold for each OS family. Until every host - especially Server 2012/2012 R2 and 2016 systems that may lag in patch cadence - is updated, reduce exposure by blocking users from mounting untrusted removable media: enforce Group Policy or Intune removable-storage deny rules and disable autorun/automount (the trade-off is loss of legitimate USB storage and easier mounting of approved volumes, which must be handled through an allow-list or an endpoint-management exception). Environments that do not need exFAT can disable the driver entirely (for example by setting the exFAT service/filesystem driver start value to disabled and blocking the exFAT driver load via a policy or attack-surface-reduction rule), accepting that exFAT-formatted SD cards, cameras and external drives will no longer mount. Where removable file systems are unavoidable, route them through a managed workflow - mount images/VHDs only in an isolated VM or sandbox with no access to production credentials, and monitor for unexpected exFAT driver faulting or pool-corruption events as an early indicator. These are compensating controls only; the build-level updates above are the definitive fix.
Affected VersionsENISA
Affected Packages
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
exFAT is the file system Microsoft introduced for flash media and large removable volumes, and it is implemented in kernel-mode Windows driver code that mounts and parses on-disk structures - boot sector and volume metadata, FAT/allocation bitmaps, directory entry sets and the upcase table - supplied entirely by whoever formatted the volume. The flaw is a heap-based buffer overflow (CWE-122), meaning a size or length value taken from attacker-controlled exFAT metadata is used for a heap allocation or bounds check that does not match the subsequent copy, allowing kernel-pool memory beyond the intended buffer to be overwritten. Because the driver runs in kernel mode (ring 0), corrupting that heap memory crosses the user-to-kernel privilege boundary, which is why the vector is AV:L/PR:L with High confidentiality, integrity and availability impact rather than any network component: the attacker needs existing local access to plant and mount the malicious volume. Authentication requirements are confirmed from the assessed vector as authenticated low privilege (PR:L), and no separate victim interaction is modeled (UI:N). No CPE strings were supplied with this report; the affected build ranges in the accompanying EUVD data identify the specific Windows 10, Windows 11 and Windows Server platforms, all of which ship the same exFAT driver code path.
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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only exFAT parsing (AV:L) reliably reachable by an authenticated low-privilege user (PR:L, AC:L); kernel-level EoP yields full C/I/A impact with unchanged scope.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows exFAT File System allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A heap-based buffer overflow in the Windows exFAT file system driver (CVE-2026-85822, CVSS 7.8) lets any authenticated user on a Windows 10, Windows 11, or Windows Server 2012-2025 host escalate to SYSTEM/kernel privileges by having the driver parse a crafted exFAT-formatted USB device, disk image, or VHD. Because the vulnerable driver ships with the operating system, the exposure spans effectively the entire Windows estate rather than a single application, and any user with an ordinary account - including contractors, shared-workstation users, and help-desk staff - is a potential entry point. Leadership should treat this as a routine but urgent patch-now item: it is local-only (confirmed actively exploited is not applicable - no public exploit identified at time of analysis), so the near-term risk is internal privilege escalation and lateral movement rather than remote compromise, and it is fully addressable with vendor patches.
Apply vendor patch.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
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
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
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
EUVD-2026-99531
GHSA-g78m-c7pv-2vfc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB