CVE-2026-50412
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 · uneditedStack-based buffer overflow in Windows NTFS allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceA stack-based buffer overflow vulnerability in the Windows NTFS file system driver allows a local authenticated attacker to execute arbitrary code with elevated SYSTEM privileges by overflowing a stack-based buffer in the kernel-mode NTFS driver.
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< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2525all versions= r2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows 10 build versionOpen Command Prompt and run: winver or systeminfo | findstr /B /C:"OS Version"Affected if The build number is less than 14393.9339 (1607), 17763.9020 (1809), 19044.7548 (21h2), or 19045.7548 (22h2)
-
Check Windows 11 build versionOpen Command Prompt and run: winver or systeminfo | findstr /B /C:"OS Version"Affected if The build number is less than 26100.8875 (24h2), 26200.8875 (25h2), or 28000.2525 (26h1)
-
Check Windows Server 2012/R2 versionOpen Command Prompt and run: winver or systeminfo | findstr /B /C:"OS Name"Affected if The system is Windows Server 2012 or Windows Server 2012 R2 (all versions are affected)
-
Verify NTFS file system is in useOpen Command Prompt and run: fsutil fsinfo volumeinfo C: (or any local NTFS volume)Affected if The file system is NTFS (required for the vulnerable driver to be engaged)
-
Confirm current user contextRun: whoami /groups | findstr "S-1-5-18" or check if running as AdministratorAffected if The current user is a local administrator or has interactive logon rights (prerequisite for local exploitation)
-
Check ntfs.sys driver versionNavigate to C:\Windows\System32\drivers\ntfs.sys, right-click Properties, view Version tab, or run: wmic datafile where "name='C:\\\\Windows\\\\System32\\\\drivers\\\\ntfs.sys'" get VersionAffected if The driver version is older than the corresponding patched build for your Windows version
Your environment is affected if you run any Windows 10 version before the listed builds, Windows 11 before 10.0.28000.2525, or Windows Server 2012/R2, and the system uses NTFS with an authenticated local user present.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data10.0.14393.933910.0.17763.902010.0.19044.7548
Apply Microsoft security updates for Windows when released; until then, restrict local system access to trusted administrators and monitor for signs of local privilege escalation attempts.
- Consultation8.0 h
- Implementation2.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,704.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50412 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50412 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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