dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-40380

MEDIUM · 6.2 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
64/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in Volume Manager Extension Driver allows an authorized attacker to execute code with a physical attack.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap-based buffer overflow vulnerability exists in the Volume Manager Extension Driver. The flaw allows an authorized attacker with physical access to the system to execute arbitrary code by overflowing a heap-allocated buffer, potentially escalating privileges or achieving code execution within the kernel or system context.

MitigationApply vendor-supplied patches for the Volume Manager Extension Driver. Until a patch is available, limit physical access to affected systems and monitor for suspicious driver behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number
    Affected if The build number is lower than the fixed version for your Windows release (14393.9140, 17763.8755, 19044.7291, 19045.7291, 22631.7079, 26100.8390, 26200.8390, or 28000.2113)
  2. Identify Volume Manager Extension Driver
    Run 'driverquery /v | findstr -i volmgr' or check C:\Windows\System32\drivers\volmgrx.sys for presence
    Affected if The Volume Manager Extension Driver (volmgrx.sys) exists on the system
  3. Check driver version
    Right-click volmgrx.sys in System32\drivers, select Properties, then Details to view file version, or use 'powershell (Get-Item C:\Windows\System32\drivers\volmgrx.sys).VersionInfo'
    Affected if The driver file version is lower than the version corresponding to the patched Windows build for your release
  4. Verify driver loaded status
    Run 'sc query volmgr' or check Device Manager under "Volume Manager" in the system devices list
    Affected if The Volume Manager Extension Driver is currently loaded or installed on the system

A system is affected if it runs an unpatched Windows version listed in the affected ranges AND has the Volume Manager Extension Driver loaded, with physical access being the attack vector requirement.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply vendor-supplied patches for the Volume Manager Extension Driver. Until a patch is available, limit physical access to affected systems and monitor for suspicious driver behavior.

Recommended fix High confidence

Install the corresponding Microsoft security update (KB) for CVE-2026-40380 from Windows Update or Microsoft Update Catalog - the fixed build numbers are: Windows 10 1607 (10.0.14393.9140), Windows 10 1809 (10.0.17763.8755), Windows 10 21h2 (10.0.19044.7291), Windows 10 22h2 (10.0.19045.7291), Windo

  1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo'
  2. Navigate to Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2026-40380
  3. Download and install the specific security update KB for your Windows version from Microsoft Update Catalog
  4. Restart the system after applying the update
  5. Verify the installation by checking the installed updates list or running 'systeminfo' to confirm the build number matches or exceeds the fixed version for your release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data