dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50690

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 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
Use of uninitialized resource in Windows SMB 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

This is a local information disclosure vulnerability in Windows SMB (Server Message Block) protocol. The flaw involves the use of an uninitialized resource, which can leak sensitive memory contents to an authorized local attacker. The CVSS 5.5 score indicates moderate severity with local attack vector and low attack complexity.

MitigationApply the relevant Microsoft security update for Windows SMB to remediate this vulnerability. Since this is a local information disclosure issue, prioritize patching systems that handle sensitive data or have broad user access.

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
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 build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to get the exact build number (e.g., 10.0.19045.xxxx)
    Affected if The build number is lower than the version thresholds: 14393.9339 for 1607, 17763.9020 for 1809, 19044.7548 for 21h2, 19045.7548 for 22h2, 26100.8875 for 11 24h2, 26200.8875 for 11 25h2, or 28000.2269/28000.2525 for 11 26h1. Server 2012/R2 all versions are affected.
  2. Verify SMB service is running
    Run 'Get-Service -Name Server' in PowerShell or check Services.msc for the 'Server' (LanmanServer) service status
    Affected if The Server service is running and SMB is enabled as the attack surface must be active for exploitation
  3. Confirm SMB protocol is exposed
    Run 'Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol,EnableSMB2Protocol' in PowerShell to check if SMB is enabled
    Affected if Either SMBv1 or SMBv2/SMBv3 is enabled - the vulnerability exists within the SMB implementation itself

Your system is affected if the Windows build number is below the specified thresholds AND the SMB Server service is running.

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 the relevant Microsoft security update for Windows SMB to remediate this vulnerability. Since this is a local information disclosure issue, prioritize patching systems that handle sensitive data or have broad user access.

Recommended fix High confidence

Windows 10: Upgrade to latest supported version (22h2 with latest cumulative update); Windows 11: Upgrade to latest supported version (26h1/25h2 with latest cumulative update); Windows Server 2012/2012 R2: Migrate to Windows Server 2022 or later

  1. Install the latest Windows cumulative update for your Windows 10 or 11 version via Windows Update or WSUS
  2. Verify SMB is properly configured: ensure SMBv1 is disabled (not needed for modern environments) by running 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' and disable if enabled
  3. Confirm the installed version meets or exceeds the fixed build: Windows 10 1607 -> 10.0.14393.9339, 1809 -> 10.0.17763.9020, 21h2 -> 10.0.19044.7548, 22h2 -> 10.0.19045.7548; Windows 11 24h2 -> 10.0.26100.8875, 25h2 -> 10.0.26200.8875, 26h1 -> 10.0.28000.2525
  4. For Windows Server 2012/2012 R2: migrate to a supported Windows Server version (2016, 2019, 2022, or 2025) as no patches are available for these end-of-life versions
Caveat Windows Server 2012/2012 R2 has no patch available - requires migration to supported OS version; SMBv1 must be disabled which may affect very legacy clients if still in use

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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