CyberSecBulletin
CVE-2026-32093NVD status: Analyzed

Windows 10 Version 1607: Heap-based Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2026-32093 is a high-severity heap-based buffer overflow vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.14393.9060 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.16% chance of exploitation within 30 days, higher than 68% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Windows 10 Version 1607 to 10.0.14393.9060 or a later version.
  2. Update Windows 10 Version 1809 to 10.0.17763.8644 or a later version.
  3. Update Windows 10 Version 21H2 to 10.0.19044.7184 or a later version.
  4. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.906010.0.14393.9060
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.864410.0.17763.8644
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.718410.0.19044.7184
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.718410.0.19045.7184
MicrosoftWindows 11 version 23H210.0.22631.0 up to, but not including, 10.0.22631.693610.0.22631.6936
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.824610.0.26100.8246
MicrosoftWindows 11 Version 25H210.0.26200.0 up to, but not including, 10.0.26200.824610.0.26200.8246
MicrosoftWindows 11 version 26H110.0.28000.0 up to, but not including, 10.0.28000.183610.0.28000.1836
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.260266.2.9200.26026
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.260266.2.9200.26026
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.231326.3.9600.23132
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.231326.3.9600.23132
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.906010.0.14393.9060
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.906010.0.14393.9060
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.864410.0.17763.8644
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.864410.0.17763.8644
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.502010.0.20348.5020
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0 up to, but not including, 10.0.25398.227410.0.25398.2274
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.3269010.0.26100.32690
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.3269010.0.26100.32690
MicrosoftWindows 10 1607before 10.0.14393.906010.0.14393.9060
MicrosoftWindows 10 1809before 10.0.17763.864410.0.17763.8644
MicrosoftWindows 10 21h2before 10.0.19044.718410.0.19044.7184
MicrosoftWindows 10 22h2before 10.0.19045.718410.0.19045.7184
MicrosoftWindows 11 23h2before 10.0.22631.693610.0.22631.6936

Version data comes from the organisation that assigned the CVE; 4 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).

Official description

Concurrent execution using shared resource with improper synchronization ('race condition') in Function Discovery Service (fdwsd.dll) allows an authorized attacker to elevate privileges locally.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Heap-based Buffer Overflow

The product writes past the end of a buffer that was allocated on the heap.

How developers prevent this class of flaw

  • Pre-design: Use a language or compiler that performs automatic bounds checking.
  • Use an abstraction library to abstract away risky APIs. Not a complete solution.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Heap-based Buffer Overflow vulnerabilities (CWE-122)

Timeline

  1. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  2. CVE record published.
  3. Record last changed materially (score, affected products, status or references).

References

Recent Heap-based Buffer Overflow vulnerabilities

Spotted an error? Tell us.