dbcve.org
Windows AppApplication · Microsoft

CVE-2026-42992

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 2.0.1193.0 / 10.0.14393.9234 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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
Heap-based buffer overflow in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

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

Heap-based buffer overflow vulnerability in Remote Desktop Client enabling remote code execution by unauthenticated attacker over network. This is a memory corruption vulnerability in client-side RDP software that could allow attacker to execute arbitrary code on connected client systems.

MitigationApply vendor patches for Remote Desktop Client when available; restrict network access to untrusted RDP servers; consider network segmentation to limit exposure of RDP clients to potentially malicious servers.

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 AppApplication
Affected:< 2.0.1193.0
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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 and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows 10 or 11 version and build
    Affected if The build number is lower than the fixed version for your Windows release (e.g., < 10.0.19045.7417 for Windows 10 22h2, < 10.0.22631.7219 for Windows 11 23h2, etc.)
  2. Check Remote Desktop Client (mstsc.exe) version
    Navigate to C:\Windows\System32\mstsc.exe, right-click and select Properties, then check the File Version on the Details tab; or run '(Get-Item C:\Windows\System32\mstsc.exe).VersionInfo' in PowerShell
    Affected if The file version is lower than the corresponding Windows build version fix listed for your OS release
  3. Check Windows App Remote Desktop version if used
    Open Microsoft Store, go to Library, find Remote Desktop and check version; or run 'Get-AppxPackage *RemoteDesktop* | Select-Object Name, Version' in PowerShell
    Affected if The installed Microsoft Remote Desktop app version is less than 2.0.1193.0
  4. Confirm RDP client is in use
    Verify that the Remote Desktop Client (mstsc.exe) or Windows App Remote Desktop is present and executable on the system
    Affected if The RDP client software is installed and available for connections

The system is affected if the installed Windows build or RDP client version falls below the fixed version thresholds for the corresponding Windows release, and the Remote Desktop Client is in use.

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 2.0.1193.0 / 10.0.14393.9234 / 10.0.17763.8880 or later
Fixed in 2.0.1193.010.0.14393.923410.0.17763.8880
Interim mitigation

Apply vendor patches for Remote Desktop Client when available; restrict network access to untrusted RDP servers; consider network segmentation to limit exposure of RDP clients to potentially malicious servers.

Recommended fix High confidence

Windows App: 2.0.1193.0 or later | Windows 10 1607: 10.0.14393.9234 or later | Windows 10 1809: 10.0.17763.8880 or later | Windows 10 21h2: 10.0.19044.7417 or later | Windows 10 22h2: 10.0.19045.7417 or later | Windows 11 23h2: 10.0.22631.7219 or later | Windows 11 24h2: 10.0.26100.8655 or later | W

  1. Open Windows Settings on the affected machine
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' and install all available updates
  4. Alternatively, manually download and install the specific security update from the Microsoft Update Catalog matching your Windows version (search for the CVE KB article)
  5. Restart the system after updates are installed
  6. Verify the update was successful by running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update process has minimal risk; ensure backups of critical data before applying updates in production environments

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

Fix this in Windows App Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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