dbcve.org
Remote Desktop ClientApplication · Microsoft

CVE-2026-42913

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 1.2.7214 / 10.0.20348.5256 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
Concurrent execution using shared resource with improper synchronization ('race condition') 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

A race condition vulnerability exists in the Remote Desktop Client due to improper synchronization when accessing shared resources. This concurrent execution flaw allows an unauthenticated attacker to execute arbitrary code remotely over a network by exploiting the timing window in the synchronization logic.

MitigationApply vendor-provided security patches for the Remote Desktop Client when released. Until a patch is available, restrict network exposure of RDP clients and monitor for anomalous client behavior.

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
Remote Desktop ClientApplication
Affected:< 1.2.7214
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
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269
Windows Server 2022Operating system
Affected:< 10.0.20348.5256
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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 if Remote Desktop Client is installed
    Open Command Prompt and run: mstsc.exe /version or check for mstsc.exe in System32 folder (C:\Windows\System32\mstsc.exe)
    Affected if The client executable exists on the system
  2. Determine Remote Desktop Client version
    Right-click mstsc.exe in System32, select Properties, and view the File Version under the Details tab. Alternatively, run: powershell (Get-Item 'C:\Windows\System32\mstsc.exe').VersionInfo
    Affected if Version is less than 1.2.7214 (for standalone Remote Desktop Client installations)
  3. Check Windows 11 version
    Run: winver or go to Settings > System > About to view the Windows version and build number
    Affected if Running Windows 11 23h2 with build < 10.0.22631.7219, 24h2 with build < 10.0.26100.8655, 25h2 with build < 10.0.26200.8655, or 26h1 with build < 10.0.28000.2269
  4. Check Windows Server version
    Run: winver or run 'systeminfo' in Command Prompt and look at the OS Version and Build Number
    Affected if Running Windows Server 2022 with build < 10.0.20348.5256 or Windows Server 2025 with build < 10.0.26100.32995

The system is affected if the Remote Desktop Client version is below 1.2.7214, or if running a Windows version with a build number lower than the specified threshold for the respective version.

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 1.2.7214 / 10.0.20348.5256 / 10.0.22631.7219 or later
Fixed in 1.2.721410.0.20348.525610.0.22631.7219
Interim mitigation

Apply vendor-provided security patches for the Remote Desktop Client when released. Until a patch is available, restrict network exposure of RDP clients and monitor for anomalous client behavior.

Recommended fix High confidence

Remote Desktop Client 1.2.7214 or later | Windows 11 23h2 build 10.0.22631.7219 or later | Windows 11 24h2 build 10.0.26100.8655 or later | Windows 11 25h2 build 10.0.26200.8655 or later | Windows 11 26h1 build 10.0.28000.2269 or later | Windows Server 2022 build 10.0.20348.5256 or later | Windows S

  1. Open Windows Update Settings (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security updates
  3. Restart the system if prompted to complete the installation
  4. Verify the installed build version matches or exceeds the fixed version for your Windows edition
  5. For enterprise environments, deploy the relevant cumulative update via WSUS or Microsoft Update Catalog: Windows 11 23h2 (KB5048680), Windows 11 24h2 (KB5048702), Windows Server 2022 (KB5048685), or Windows Server 2025 (KB5048703)
Caveat Standard Windows update with no expected breaking changes; as a client-side Remote Desktop vulnerability, no server configuration changes are required

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

Fix this in Remote Desktop Client Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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