dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-58535

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 unauthorized 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 · high confidence

This is an information disclosure vulnerability in Windows Remote Desktop Protocol (RDP) stemming from the use of an uninitialized resource. An unauthorized remote attacker can exploit this over a network to potentially reveal sensitive information from the affected Windows system.

MitigationApply the relevant Microsoft Windows security update to patch the uninitialized resource vulnerability in RDP. Prioritize externally-facing systems with RDP exposure.

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

CVSS:3.1/AV:N/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. Verify RDP is enabled
    Open PowerShell and run: Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' | Select-Object -ExpandProperty fDenyTSConnections. A value of 0 means RDP is enabled.
    Affected if The value returned is 0, indicating RDP is enabled on this system.
  2. Check Windows 10 version 1607 build number
    Run: winver or 'systeminfo | findstr /C:"Build"'. Compare the build number to 10.0.14393.9339.
    Affected if Running Windows 10 1607 with build number less than 14393.9339.
  3. Check Windows 10 version 1809 build number
    Run: winver or 'systeminfo | findstr /C:"Build"'. Compare the build number to 10.0.17763.9020.
    Affected if Running Windows 10 1809 with build number less than 17763.9020.
  4. Check Windows 10 version 21h2/22h2 build number
    Run: winver or 'systeminfo | findstr /C:"Build"'. Compare the build number to 10.0.19044.7548 or 10.0.19045.7548 depending on your specific version.
    Affected if Running Windows 10 21h2 with build less than 19044.7548, or Windows 10 22h2 with build less than 19045.7548.
  5. Check Windows 11 version build number
    Run: winver or 'systeminfo | findstr /C:"Build"'. Compare to affected versions: 24h2 requires 26100.8875, 25h2 requires 26200.8875, 26h1 requires 28000.2525.
    Affected if Running Windows 11 24h2 below 26100.8875, 25h2 below 26200.8875, or 26h1 below 28000.2525.
  6. Check Windows Server 2012/R2 version
    Run: winver or 'systeminfo | findstr /C:"OS"'. Windows Server 2012 and 2012 R2 are listed as all versions affected.
    Affected if Running Windows Server 2012 or Windows Server 2012 R2, regardless of build number.

The system is affected if RDP is enabled AND the Windows version/build falls within any of the affected ranges listed, or if running Windows Server 2012/R2.

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 to patch the uninitialized resource vulnerability in RDP. Prioritize externally-facing systems with RDP exposure.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.9339 or later | Windows 10 1809: build 10.0.17763.9020 or later | Windows 10 21h2: build 10.0.19044.7548 or later | Windows 10 22h2: build 10.0.19045.7548 or later | Windows 11 24h2: build 10.0.26100.8875 or later | Windows 11 25h2: build 10.0.26200.8875 or later |

  1. 1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. 2. Click 'Check for updates' to ensure you have the latest patches
  3. 3. Install any available security updates for this month
  4. 4. Alternatively, manually download and install the specific cumulative update for your Windows version from the Microsoft Update Catalog
  5. 5. For Windows Server 2012 R2, Microsoft has released a security update; obtain it from Windows Update or the Microsoft Update Catalog
  6. 6. After installation, restart the affected system
  7. 7. Verify the installed update by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update apply; no major breaking changes expected for this security patch

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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