Concurrent execution using shared resource with improper synchronization ('race condition') in Remote Desktop Client allows an unauthorized attacker to execute code over a network.
CVE-2026-42909
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 34(Track)EG Risk 34/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 32%
- KEV
- Not listed
Published
June 9, 2026
Last Modified
July 28, 2026
Advisory Details (1)
Auto-updated Jun 10, 2026Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42909Vendor Advisories for CVE-2026-42909(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 98× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 192 total refreshes for this CVE.
- 2026-07-29 11:46 UTCVendor advisory
- 2026-07-29 11:46 UTCGHSA enrichment
- 2026-07-28 22:53 UTCEG score recompute
- 2026-07-28 22:53 UTCVendor advisory
- 2026-07-28 22:53 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-28 02:42 UTCEG score recompute
- 2026-07-28 02:42 UTCVendor advisory
- 2026-07-28 02:42 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 10:05 UTCVendor advisory
- 2026-07-27 10:05 UTCGHSA enrichment
- 2026-07-26 21:12 UTCEG score recompute
- 2026-07-26 21:12 UTCVendor advisory
- 2026-07-26 21:12 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 05:57 UTCEG score recompute
- 2026-07-26 05:57 UTCVendor advisory
- 2026-07-26 05:57 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 03:12 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 00:03 UTCVendor advisory
- 2026-07-17 00:03 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 08:59 UTCVendor advisory
- 2026-07-16 08:59 UTCGHSA enrichment
- 2026-07-15 19:58 UTCVendor advisory
- 2026-07-15 19:58 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:28 UTCVendor advisory
- 2026-07-15 02:28 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 12:26 UTCVendor advisory
- 2026-07-14 12:26 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 20:27 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 02:25 UTCVendor advisory
- 2026-07-13 02:25 UTCGHSA enrichment
- 2026-07-12 11:19 UTCVendor advisory
- 2026-07-12 11:19 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:42 UTCVendor advisory
- 2026-07-11 21:41 UTCGHSA enrichment
- 2026-07-11 08:47 UTCVendor advisory
- 2026-07-11 08:47 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 19:53 UTCVendor advisory
- 2026-07-10 19:53 UTCGHSA enrichment
- 2026-07-10 00:03 UTCVendor advisory
- 2026-07-10 00:03 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 04:31 UTCVendor advisory
- 2026-07-09 04:31 UTCGHSA enrichment
- 2026-07-08 15:26 UTCVendor advisory
- 2026-07-08 15:26 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 23:35 UTCVendor advisory
- 2026-07-07 23:35 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 15:18 UTCVendor advisory
- 2026-07-05 15:18 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:24 UTCVendor advisory
- 2026-07-05 02:23 UTCGHSA enrichment
- 2026-07-04 13:30 UTCVendor advisory
- 2026-07-04 13:30 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-03 21:43 UTCVendor advisory
- 2026-07-03 21:43 UTCGHSA enrichment
- 2026-07-03 08:49 UTCVendor advisory
- 2026-07-03 08:49 UTCGHSA enrichment
- 2026-07-02 18:59 UTCVendor advisory
- 2026-07-02 18:59 UTCGHSA enrichment
- 2026-07-02 06:06 UTCVendor advisory
- 2026-07-02 06:06 UTCGHSA enrichment
- 2026-07-01 17:06 UTCVendor advisory
- 2026-07-01 17:06 UTCGHSA enrichment
- 2026-07-01 15:06 UTCEPSS rescore
- 2026-07-01 04:12 UTCVendor advisory
- 2026-07-01 04:12 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 15:19 UTCVendor advisory
- 2026-06-30 15:19 UTCGHSA enrichment
- 2026-06-29 22:41 UTCVendor advisory
- 2026-06-29 22:41 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 09:47 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-362 · CWE-787
Frequently asked(5)
What is CVE-2026-42909?
When was CVE-2026-42909 disclosed?
Is CVE-2026-42909 actively exploited?
What is the CVSS score of CVE-2026-42909?
How do I remediate CVE-2026-42909?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-42909
Is Your Infrastructure Affected by CVE-2026-42909?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.