dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-58539

HIGH · 7.5 CVSS v3.1 Developing 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
Out-of-bounds read 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-11.

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
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

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
Recommended fix High confidence

Upgrade to the respective build number: 10.0.14393.9339 (Win10 1607), 10.0.17763.9020 (Win10 1809), 10.0.19044.7548 (Win10 21h2), 10.0.19045.7548 (Win10 22h2), 10.0.26100.8875 (Win11 24h2), 10.0.26200.8875 (Win11 25h2), or 10.0.28000.2269 (Win11 26h1); migrate from Server 2012/R2 to a supported Wind

  1. 1. Identify the current Windows version and build by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. For Windows 10 1607 systems, apply update KB5055525 (build 10.0.14393.9339) or later
  3. 3. For Windows 10 1809 systems, apply update KB5055537 (build 10.0.17763.9020) or later
  4. 4. For Windows 10 21h2 systems, apply update KB5055523 (build 10.0.19044.7548) or later
  5. 5. For Windows 10 22h2 systems, apply update KB5055518 (build 10.0.19045.7548) or later
  6. 6. For Windows 11 24h2 systems, apply update KB5055527 (build 10.0.26100.8875) or later
  7. 7. For Windows 11 25h2 systems, apply update KB5055531 (build 10.0.26200.8875) or later
  8. 8. For Windows 11 26h1 systems, apply update KB5055535 (build 10.0.28000.2269) or later
Caveat Windows Server 2012/R2 has no patch available and requires migration to a supported OS version; standard Windows update compatibility considerations apply

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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