CVE-2026-42909: Remote Desktop Client Remote Code Execution Vulnerability

Published Jun 9, 2026
·
Updated

Concurrent execution using shared resource with improper synchronization ('race condition') in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

Other sources

Heap-based buffer overflow in Remote Desktop Client allows an unauthorized attacker to execute code over a network.

Microsoft

Remote Desktop Client Remote Code Execution Vulnerability

Microsoft

Affected Software

73 affected componentsFixes available
Microsoft Windows 11=23H2
Microsoft Windows 11=23H2
Microsoft Windows 10=22H2
Microsoft Windows 11=25H2
Microsoft Windows 10=22H2
Microsoft Windows Server 2025
Microsoft Windows 11=25H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Remote Desktop client for Windows Desktop
Microsoft Remote Desktop Client Windows<1.2.7214
Microsoft Windows App Windows<2.0.1193.0
Microsoft Windows 10 1607<10.0.14393.9234
Microsoft Windows 10 1607<10.0.14393.9234
Microsoft Windows 10 1809<10.0.17763.8880
Microsoft Windows 10 1809<10.0.17763.8880
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 21h2<10.0.19044.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 10 22h2<10.0.19045.7417
Microsoft Windows 11 23h2<10.0.22631.7219
Microsoft Windows 11 23h2<10.0.22631.7219
Microsoft Windows 11 24h2<10.0.26100.8655
Microsoft Windows 11 24h2<10.0.26100.8655
Microsoft Windows 11 25h2<10.0.26200.8655
Microsoft Windows 11 25h2<10.0.26200.8655
Microsoft Windows 11 26h1<10.0.28000.2269
Microsoft Windows 11 26h1<10.0.28000.2269
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9234
Microsoft Windows Server 2019<10.0.17763.8880
Microsoft Windows Server 2022<10.0.20348.5256
Microsoft Windows Server 2025<10.0.26100.32995
Microsoft Windows 10=1607
10.0.14393.9234
Microsoft Windows 11=26H1
10.0.28000.2269
Microsoft Windows 10=1607
10.0.14393.9234
Microsoft Windows 11=24H2
10.0.26100.8655
Microsoft Windows 11=26H1
10.0.28000.2269
Microsoft Windows Server 2025<10.0.26100.32995
10.0.26100.32995
Microsoft Windows 11=24H2
10.0.26100.8655
Microsoft Windows 11=23H2
10.0.22631.7219
Microsoft Windows 11=25H2
10.0.26200.8655
Microsoft Windows 11=23H2
10.0.22631.7219
Microsoft Windows 11=25H2
10.0.26200.8655
Microsoft Windows Server 2025<10.0.26100.32995
10.0.26100.32995
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Remote Desktop client for Windows Desktop<1.2.7214.0
1.2.7214.0
Microsoft Windows Server 2022<10.0.20348.5256
10.0.20348.5256
Microsoft Windows Server 2022<10.0.20348.5256
10.0.20348.5256
Microsoft Windows App Client for Windows Desktop<2.0.1193.0
2.0.1193.0
Microsoft Windows 10=22H2
10.0.19045.7417
Microsoft Windows Server 2016<10.0.14393.9234
10.0.14393.9234
Microsoft Windows 10=21H2
10.0.19044.7417
Microsoft Windows Server 2019<10.0.17763.8880
10.0.17763.8880
Microsoft Windows Server 2016<10.0.14393.9234
10.0.14393.9234
Microsoft Windows Server 2019<10.0.17763.8880
10.0.17763.8880
Microsoft Windows Server 2012 R2<6.3.9600.23228
6.3.9600.23228
Microsoft Windows Server 2012 R2<6.3.9600.23228
6.3.9600.23228
Microsoft Windows Server 2012<6.2.9200.26132
6.2.9200.26132
Microsoft Windows Server 2012<6.2.9200.26132
6.2.9200.26132
Microsoft Windows 10=1809
10.0.17763.8880
Microsoft Windows 10=1809
10.0.17763.8880

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9234Patch KB5094122
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.2269Patch KB5095051
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.8655Patch KB5094126
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.32995Patch KB5094125
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7219Patch KB5093998
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.8655Patch KB5094126
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7417Patch KB5094127
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7417Patch KB5094127
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.2.7214.0
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5256Patch KB5094128
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.0.1193.0
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.8880Patch KB5094123
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23228Patch KB5094041
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26132Patch KB5094042

Event History

Jun 9, 2026
CVE Published
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
Updated
via Microsoft·02:00 PM
WeaknessAffected Software
CVE Published
via MITRE·05:06 PM
Data Sourced
via MITRE·05:06 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-42909?

The severity of CVE-2026-42909 is rated as high, with a score of 7.5.

2

What does CVE-2026-42909 affect?

CVE-2026-42909 affects multiple versions of Microsoft Windows, including Windows 10, Windows 11, and various versions of Windows Server.

3

How do I fix CVE-2026-42909?

To fix CVE-2026-42909, you should apply the latest security updates provided by Microsoft for your Windows operating system.

4

What type of vulnerability is CVE-2026-42909?

CVE-2026-42909 is a Remote Code Execution vulnerability caused by a heap-based buffer overflow in the Remote Desktop Client.

5

Who is at risk from CVE-2026-42909?

Any unauthorized attacker with network access could exploit CVE-2026-42909 to execute arbitrary code on vulnerable systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203