dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50341

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
Zero-click Patch available 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
Buffer over-read in Windows NTFS allows an authorized attacker to disclose information 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

A buffer over-read vulnerability in Windows NTFS allows a local authorized attacker to read beyond allocated buffer boundaries, potentially disclosing sensitive information from memory. This is an information disclosure flaw in the Windows filesystem layer.

MitigationApply Microsoft security updates for Windows NTFS when released; validate the patch in a test environment to ensure NTFS operations and filesystem integrity remain unaffected.

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.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 and build number
    Open Command Prompt and run: winver OR run 'systeminfo' and look at the OS Version / Build number
    Affected if The build number is lower than the versions listed in the affected range for your Windows edition, or for Windows Server 2012/R2 any version
  2. Identify exact OS build for comparison
    Run 'ver' in Command Prompt or check HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentBuild in the registry
    Affected if Build number is less than 14393.9339 (Win10 1607), 17763.9020 (Win10 1809), 19044.7548 (Win10 21h2), 19045.7548 (Win10 22h2), 26100.8875 (Win11 24h2), 26200.8875 (Win11 25h2), 28000.2525 (Win11 26h1), or any Windows Server 2012/R2 build
  3. Confirm NTFS filesystem is in use
    Run 'fsutil fsinfo volumeinfo C:' (or any relevant drive letter) and check the 'File System Name' field
    Affected if The filesystem is NTFS (this is required for the vulnerability to be exploitable; most Windows systems use NTFS by default)
  4. Check installed security updates
    Run 'wmic qfe list' or open Settings > Windows Update > Update history to see installed patches
    Affected if No NTFS-related security update has been installed that addresses this vulnerability (patch level unknown at time of detection)

You are affected if your Windows version/build is lower than the threshold for your specific Windows edition or if running any version of Windows Server 2012/R2 with NTFS filesystem 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.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for Windows NTFS when released; validate the patch in a test environment to ensure NTFS operations and filesystem integrity remain unaffected.

Recommended fix High confidence

Latest Windows cumulative update (version numbers listed above for each affected release)

  1. Open Settings on the Windows system
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install the latest cumulative update
  4. Ensure the installed version meets or exceeds the fixed version for your Windows edition: Windows 10 1607: 10.0.14393.9339, Windows 10 1809: 10.0.17763.9020, Windows 10 21h2: 10.0.19044.7548, Windows 10 22h2: 10.0.19045.7548, Windows 11 24h2: 10.0.26100.8875, Windows 11 25h2: 10.0.26200.8875, Windows 11 26h1: 10.0.28000.2525
  5. For Windows Server 2012/2012 R2: Apply the latest cumulative update from Windows Update or Microsoft Update Catalog
  6. Restart the system after updates are installed
  7. Verify the NTFS version or build number matches or exceeds the fixed version
Caveat Standard Windows update risks - updates may require restart and could have compatibility issues with legacy applications; Windows Server 2012 R2 is approaching end of support

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
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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