dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-57982

MEDIUM · 6.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 →
71/100
Remediation priority · Elevated
Remotely reachable 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 RDP allows an authorized attacker to disclose information over a network.

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 vulnerability in Windows Remote Desktop Protocol (RDP) involves the use of an uninitialized resource, which could allow an authorized attacker to potentially disclose sensitive information over a network.

MitigationApply Microsoft security updates for Windows RDP when available; restrict RDP access to authorized users and networks using network-level authentication and firewall rules.

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

CVSS:3.1/AV:N/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 installed Windows version
    Run 'winver' from command prompt or check the registry key 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion' for the 'CurrentBuild' and 'DisplayVersion' values
    Affected if The displayed version falls within any of the affected ranges: 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.2800
  2. Confirm RDP is enabled
    Check registry key 'HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server' - verify the 'fDenyTSConnections' value is set to 0, or run 'Get-Service TermService' in PowerShell to check if the Remote Desktop Services service is running
    Affected if RDP is enabled (fDenyTSConnections = 0) or the TermService service is running, creating the attack surface for this vulnerability
  3. Verify network-level authentication requirement
    Check registry key 'HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' for the 'UserAuthentication' value (1 = NLA required, 0 = NLA not required)
    Affected if NLA is not required (UserAuthentication = 0), which would make exploitation easier, though the vulnerability exists regardless of NLA status on affected versions

You are affected if RDP is enabled and your Windows version matches any of the affected builds listed, regardless of NLA configuration, with Windows Server 2012/2012 R2 being affected at all versions.

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 Microsoft security updates for Windows RDP when available; restrict RDP access to authorized users and networks using network-level authentication and firewall rules.

Recommended fix High confidence

Windows 10 1607 to build 10.0.14393.9339 or later; Windows 10 1809 to build 10.0.17763.9020 or later; Windows 10 21h2 to build 10.0.19044.7548 or later; Windows 10 22h2 to build 10.0.19045.7548 or later; Windows 11 24h2 to build 10.0.26100.8875 or later; Windows 11 25h2 to build 10.0.26200.8875 or l

  1. 1. Identify the exact Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. For Windows 10 (1607, 1809, 21h2, 22h2): Use Windows Update to install the cumulative update that includes build 10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, or 10.0.19045.7548 respectively, or manually download the update from Microsoft Update Catalog
  3. 3. For Windows 11 (24h2, 25h2, 26h1): Use Windows Update to install the cumulative update that includes build 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2525 respectively, or manually download from Microsoft Update Catalog
  4. 4. For Windows Server 2012 R2: This version has no patch available; migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
  5. 5. After installation, restart the affected system
  6. 6. Verify the installed build matches or exceeds the fixed version by running 'winver'
Caveat Windows Server 2012 R2 has no patch and reached end of support - migration to newer OS required; upgrading Windows 10 may require application compatibility testing

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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