dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50294

MEDIUM · 6.2 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 →
67/100
Remediation priority · Elevated
No privileges 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
Exposure of sensitive system information to an unauthorized control sphere in Windows Kernel allows an unauthorized 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

This is a local information disclosure vulnerability in the Windows Kernel that allows an unauthorized attacker to gain access to sensitive system information. The vulnerability stems from improper access controls within the kernel that fail to properly restrict exposure of sensitive data to unauthorized processes or users.

MitigationApply the appropriate Microsoft Windows security update for this CVE through Windows Update or enterprise patch management systems. Verify that all affected Windows systems have received the kernel patch and confirm the vulnerability is remediated.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/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 using systeminfo
    Run `systeminfo` in Command Prompt and look at the "OS Version" line, or run `winver` to see the full version number
    Affected if The displayed version is lower than the fix version for your Windows release (e.g., for Windows 10 22h2, versions below 10.0.19045.7548 are affected)
  2. Check Windows version using PowerShell
    Run `Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer` in PowerShell
    Affected if The WindowsVersion number is below the affected threshold for your Windows release
  3. Check build number via Registry
    Run `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild` and `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v UBR` in Command Prompt
    Affected if The combined build number (CurrentBuild.UBR) is below the fixed version for your Windows edition
  4. Identify Windows 10 release
    Run `winver` or check Settings > System > About to identify if you are on 1607, 1809, 21h2, or 22h2
    Affected if The release is 1607, 1809, 21h2, or 22h2 and the version is below the specific fix listed in the affected versions
  5. Check if Windows Server 2012
    Run `systeminfo` and look for "Windows Server 2012" in the OS Name
    Affected if The system is Windows Server 2012 or Windows Server 2012 R2 (all versions are affected)

Your system is affected if it runs any Windows 10/11 version or Windows Server 2012 listed in the affected products with a version below the specified fix thresholds, or if it is Windows Server 2012 R2 at any version.

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 the appropriate Microsoft Windows security update for this CVE through Windows Update or enterprise patch management systems. Verify that all affected Windows systems have received the kernel patch and confirm the vulnerability is remediated.

Recommended fix High confidence

Install the latest Windows Security Update (KB) for your specific Windows version that includes the fix for CVE-2026-50294 - minimum fixed builds: 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 24

  1. Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Identify your Windows edition (Home, Pro, Enterprise, etc.)
  3. Open Settings > Windows Update > Check for updates
  4. Install all available security updates, specifically looking for the KB article addressing CVE-2026-50294
  5. Alternatively, manually download the security update from Microsoft Update Catalog by searching for the specific KB number for your Windows version
  6. Restart the system after installing updates
  7. Verify the installation by checking that the version matches or exceeds the fixed build number for your Windows version
Caveat Standard Windows update process has minimal risk; ensure backups of critical data before major updates; Windows Server 2012/R2 requires paid Extended Security Updates (ESU) as mainstream support has ended

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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