dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-45636

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 Windows NTFS allows an unauthorized attacker to execute code locally.

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 Windows NTFS file system driver, allowing a local attacker to achieve code execution with elevated privileges. The vulnerability stems from improper bounds checking when handling certain NTFS filesystem operations.

MitigationApply available Microsoft security patches for Windows NTFS when released. Until a patch is available, restrict local access to untrusted users and monitor for suspicious filesystem operations.

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.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Identify Windows version and build number
    Run `systeminfo` or `winver` from command prompt and note the OS Name and OS Version / Build number
    Affected if The displayed build number falls below any of these thresholds: 14393.9234, 17763.8880, 19044.7417, 19045.7417, 22631.7219, 26100.8655, 26200.8655, or 28000.2269 depending on your Windows release
  2. Verify NTFS is the active file system
    Run `fsutil fsinfo volumeinfo C:` and check the File System Name output; or open Disk Management and verify the system drive is formatted as NTFS
    Affected if The file system is NTFS (this is the default for most Windows installations)
  3. Check NTFS driver version
    Locate the ntfs.sys driver file (typically in C:\Windows\System32\drivers\) and view its file properties, or run `driverquery /v | findstr ntfs` to list the NTFS driver module
    Affected if The driver version matches a build number below the fixed versions listed for your Windows release

Your environment is affected if you are running any of the listed Windows 10 or 11 versions with a build number lower than the specified threshold and the NTFS file system is in use.

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.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply available Microsoft security patches for Windows NTFS when released. Until a patch is available, restrict local access to untrusted users and monitor for suspicious filesystem operations.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.9234 | Windows 10 1809: 10.0.17763.8880 | Windows 10 21h2: 10.0.19044.7417 | Windows 10 22h2: 10.0.19045.7417 | Windows 11 23h2: 10.0.22631.7219 | Windows 11 24h2: 10.0.26100.8655 | Windows 11 25h2: 10.0.26200.8655 | Windows 11 26h1: 10.0.28000.2269

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if the installed version is below the fixed version for your Windows release
  3. Apply the relevant Microsoft security patch via Windows Update (Settings > Update & Security > Windows Update > Check for updates)
  4. Alternatively, download the security update manually from the Microsoft Update Catalog for your specific Windows version
  5. After installation, restart the system to complete the patch
  6. Verify the update was successful by checking the installed OS version matches or exceeds the fixed version number
Caveat Standard Windows update - minimal risk; ensure backups of critical data before applying

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45636 — 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-45636 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