CVE-2026-57979
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 · uneditedOut-of-bounds read in Windows RDP allows an unauthorized attacker to disclose information over a network.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
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 confidenceAn out-of-bounds read vulnerability in Windows Remote Desktop Protocol allows unauthenticated remote attackers to read sensitive memory contents beyond intended buffer boundaries, potentially disclosing confidential information from the targeted system.
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< 10.0.14393.9339< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26200.8875< 10.0.28000.2525all versions= r2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Windows version and build numberOpen Command Prompt and run 'systeminfo' or 'winver' to see the installed Windows version and build number (e.g., 10.0.19045.xxxx)Affected if The installed build number is lower than the threshold for your Windows release: Windows 10 1607 requires <10.0.14393.9339, 1809 requires <10.0.17763.9020, 21h2 requires <10.0.19044.7548, 22h2 requires <10.0.19045.7548; Windows 11 24h2 requires <10.0.26100.8875, 25h2 requires <10.0.26200.8875, 26h1
-
Verify Remote Desktop Protocol is enabledOpen Registry Editor and navigate to 'HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server', or run 'reg query HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server /v fDenyTSConnections'Affected if The value fDenyTSConnections is set to 0 (RDP enabled); if set to 1, RDP is disabled and the system is not vulnerable to this flaw
-
Confirm RDP is listening on network interfacesOpen Command Prompt and run 'netstat -ano | findstr :3389' to see if port 3389 is listening, or check Windows Firewall rules for inbound RDP connectionsAffected if Port 3389 is listening on any IP address (0.0.0.0 or external adapter) rather than localhost only; if RDP is enabled but not listening on network interfaces, exposure is reduced
You are affected if your Windows version build number is below the threshold AND Remote Desktop Protocol is enabled and listening on accessible network interfaces.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.933910.0.17763.902010.0.19044.7548
Apply the applicable Microsoft security update for this CVE to resolve the out-of-bounds read in RDP. Additionally, restrict RDP exposure to trusted networks only, or disable RDP if not business-critical, as a compensating control until patching is complete.
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 2012 R2: Apply latest ESU patch o
- Open Windows Settings on the affected system
- Navigate to Update & Security > Windows Update
- Click 'Check for updates' and install all available updates
- Alternatively, download updates from the Microsoft Update Catalog (catalog.update.microsoft.com) by searching for the specific KB for your Windows version
- For Windows Server 2012 R2, which is end-of-support, check Microsoft's Extended Security Updates (ESU) program or consider upgrading to a supported Windows Server version
- Restart the system after installing updates
- Verify the installed version matches or exceeds the fixed build number for your Windows version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57979 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57979 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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