dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50681

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
Exposure of sensitive information to an unauthorized actor in Windows Cryptographic Services 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 Cryptographic Services where an authorized attacker can access sensitive cryptographic information they should not have access to. The vulnerability has a medium confidentiality impact with no integrity or availability changes, consistent with a local privilege boundary weakness.

MitigationApply the relevant Microsoft Windows security update for this vulnerability through standard patch management processes.

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 2016Operating system
Affected:< 10.0.14393.9339

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 using winver command
    Open Command Prompt and run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
    Affected if The displayed Windows version falls below any of these thresholds: Windows 10 1607/Server 2016 < 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, or Windows
  2. Verify exact build number
    Run `winver` and note the full build number (for example, 10.0.19045.xxxx) or run `reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild`
    Affected if The build number is lower than the version thresholds listed in step 1
  3. Confirm Windows edition and service pack status
    Run `systeminfo` and check the OS Name and OS Configuration lines to confirm edition (Pro, Enterprise, Server, etc.)
    Affected if Running an affected edition and version listed in the CVE advisory
  4. Identify if Cryptographic Services are in use
    Check if the Cryptographic Services service is running: open Services console (services.msc) or run `sc query CryptSvc`
    Affected if The service exists and is running on an affected Windows version (the vulnerability exists in Windows cryptographic services)

You are affected if your Windows version (including Windows 10, Windows 11, or Windows Server 2016) has a build number lower than the specific thresholds listed for your product, and the system utilizes Windows Cryptographic Services.

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 Windows security update for this vulnerability through standard patch management processes.

Recommended fix Moderate confidence

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 | Windows Server 2016: 10.0.14393.9339

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Settings > Windows Update or run 'ms-settings:windowsupdate'
  3. Check for updates and install all available cumulative updates
  4. Verify the installed build number matches or exceeds the fixed version for your Windows edition: Windows 10 1607/Server 2016 requires 10.0.14393.9339, Windows 10 1809 requires 10.0.17763.9020, Windows 10 21h2 requires 10.0.19044.7548, Windows 10 22h2 requires 10.0.19045.7548, Windows 11 24h2 requires 10.0.26100.8875, Windows 11 25h2 requires 10.0.26200.8875, Windows 11 26h1 requires 10.0.28000.252
  5. Restart the system after updates are installed
  6. Confirm the vulnerability is remediated by checking the installed version matches or exceeds the fixed build
Caveat Standard Windows update risks apply - ensure backups exist and test in staging environment before broad deployment

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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