dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50308

HIGH · 7.8 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
81/100
Remediation priority · High
No privileges 5 weeks old

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
Integer underflow (wrap or wraparound) in Windows NTFS allows an unauthorized attacker to execute code locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

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

Integer underflow vulnerability in Windows NTFS filesystem driver allows local attackers to execute arbitrary code due to improper integer arithmetic validation when processing certain filesystem operations.

MitigationApply Microsoft security patches for Windows NTFS when released; prioritize patch deployment on affected endpoints and servers.

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.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

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. Determine Windows build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the full Windows build version
    Affected if Build number falls below the threshold for your Windows version (see version-specific thresholds)
  2. Check Windows version and build
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v BuildLabEx' or 'ver' command to get exact version string
    Affected if Version matches affected Windows 10 or Windows 11 releases AND build is lower than the specified threshold
  3. Identify NTFS driver presence
    Run 'driverquery /v | findstr NTFS' or check 'C:\Windows\System32\drivers\NTFS.sys' existence
    Affected if NTFS.sys driver is present on the system (required for vulnerability)
  4. Verify NTFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo C:' to confirm NTFS filesystem is active on system drives
    Affected if System drive uses NTFS filesystem (vulnerability applies to NTFS operations)
  5. Confirm Windows Server 2012/R2 status
    Run 'systeminfo' and check if OS is Windows Server 2012 or Server 2012 R2
    Affected if Operating system is Windows Server 2012 or Server 2012 R2 (all versions affected)

System is affected if it runs a vulnerable Windows version/build (below threshold) with NTFS filesystem and the NTFS driver present.

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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security patches for Windows NTFS when released; prioritize patch deployment on affected endpoints and servers.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9339 | Windows 10 1809: build 10.0.17763.9020 | Windows 10 21h2: build 10.0.19044.7548 | Windows 10 22h2: build 10.0.19045.7548 | Windows 11 24h2: build 10.0.26100.8875 | Windows 11 25h2: build 10.0.26200.8875 | Windows 11 26h1: build 10.0.28000.2525 | Windows Serve

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine the specific build number by running 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  3. For Windows 10 1607 (build < 10.0.14393): Upgrade to build 10.0.14393.9339 or later via Windows Update or Media Creation Tool
  4. For Windows 10 1809 (build < 10.0.17763): Upgrade to build 10.0.17763.9020 or later
  5. For Windows 10 21h2 (build < 10.0.19044): Upgrade to build 10.0.19044.7548 or later
  6. For Windows 10 22h2 (build < 10.0.19045): Upgrade to build 10.0.19045.7548 or later
  7. For Windows 11 24h2 (build < 10.0.26100): Upgrade to build 10.0.26100.8875 or later
  8. For Windows 11 25h2 (build < 10.0.26200): Upgrade to build 10.0.26200.8875 or later
Caveat Windows Server 2012/2012 R2 has reached end of support; requires migration to newer Windows Server version; standard Windows update compatibility considerations apply

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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