CVE-2026-42913

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
38.2%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security 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-42913

Vendor Advisories for CVE-2026-42913(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 8× in last 7d / 104× 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 181 total refreshes for this CVE.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:12 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-17 00:03 UTCVendor advisory
  11. 2026-07-17 00:02 UTCGHSA enrichment
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-16 08:59 UTCVendor advisory
  14. 2026-07-16 08:59 UTCGHSA enrichment
  15. 2026-07-15 19:57 UTCVendor advisory
  16. 2026-07-15 19:57 UTCGHSA enrichment
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 02:27 UTCVendor advisory
  19. 2026-07-15 02:27 UTCGHSA enrichment
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-14 12:24 UTCVendor advisory
  22. 2026-07-14 12:24 UTCGHSA enrichment
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 20:27 UTCGHSA enrichment
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 75 more
  1. 2026-07-13 02:25 UTCVendor advisory
  2. 2026-07-13 02:25 UTCGHSA enrichment
  3. 2026-07-12 08:02 UTCVendor advisory
  4. 2026-07-12 08:02 UTCGHSA enrichment
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 19:36 UTCVendor advisory
  7. 2026-07-11 19:36 UTCGHSA enrichment
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 07:56 UTCVendor advisory
  10. 2026-07-11 07:56 UTCGHSA enrichment
  11. 2026-07-10 19:53 UTCVendor advisory
  12. 2026-07-10 19:53 UTCGHSA enrichment
  13. 2026-07-10 00:03 UTCVendor advisory
  14. 2026-07-10 00:02 UTCGHSA enrichment
  15. 2026-07-09 19:10 UTCEPSS rescore
  16. 2026-07-09 11:12 UTCVendor advisory
  17. 2026-07-09 11:12 UTCGHSA enrichment
  18. 2026-07-08 23:30 UTCVendor advisory
  19. 2026-07-08 23:30 UTCGHSA enrichment
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 11:18 UTCVendor advisory
  22. 2026-07-08 11:18 UTCGHSA enrichment
  23. 2026-07-07 23:35 UTCVendor advisory
  24. 2026-07-07 23:34 UTCGHSA enrichment
  25. 2026-07-07 13:46 UTCEPSS rescore
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 02:23 UTCEPSS rescore
  29. 2026-07-06 02:23 UTCEPSS rescore
  30. 2026-07-06 02:06 UTCVendor advisory
  31. 2026-07-06 02:06 UTCGHSA enrichment
  32. 2026-07-05 14:25 UTCVendor advisory
  33. 2026-07-05 14:25 UTCGHSA enrichment
  34. 2026-07-05 02:30 UTCEPSS rescore
  35. 2026-07-05 02:20 UTCVendor advisory
  36. 2026-07-05 02:20 UTCGHSA enrichment
  37. 2026-07-04 13:30 UTCVendor advisory
  38. 2026-07-04 13:29 UTCGHSA enrichment
  39. 2026-07-04 06:31 UTCEPSS rescore
  40. 2026-07-03 15:37 UTCVendor advisory
  41. 2026-07-03 15:37 UTCGHSA enrichment
  42. 2026-07-03 01:48 UTCVendor advisory
  43. 2026-07-03 01:47 UTCGHSA enrichment
  44. 2026-07-02 14:07 UTCVendor advisory
  45. 2026-07-02 14:07 UTCGHSA enrichment
  46. 2026-07-02 02:27 UTCVendor advisory
  47. 2026-07-02 02:27 UTCGHSA enrichment
  48. 2026-07-01 15:06 UTCEPSS rescore
  49. 2026-07-01 14:47 UTCVendor advisory
  50. 2026-07-01 14:47 UTCGHSA enrichment
  51. 2026-07-01 03:00 UTCVendor advisory
  52. 2026-07-01 03:00 UTCGHSA enrichment
  53. 2026-06-30 23:22 UTCEPSS rescore
  54. 2026-06-30 15:19 UTCVendor advisory
  55. 2026-06-30 15:19 UTCGHSA enrichment
  56. 2026-06-29 23:14 UTCVendor advisory
  57. 2026-06-29 23:14 UTCGHSA enrichment
  58. 2026-06-29 14:06 UTCEPSS rescore
  59. 2026-06-29 11:34 UTCVendor advisory
  60. 2026-06-29 11:34 UTCGHSA enrichment
  61. 2026-06-28 23:53 UTCVendor advisory
  62. 2026-06-28 23:53 UTCGHSA enrichment
  63. 2026-06-28 14:07 UTCEPSS rescore
  64. 2026-06-28 12:13 UTCVendor advisory
  65. 2026-06-28 12:12 UTCGHSA enrichment
  66. 2026-06-28 04:56 UTCEPSS rescore
  67. 2026-06-28 00:29 UTCVendor advisory
  68. 2026-06-28 00:29 UTCGHSA enrichment
  69. 2026-06-27 12:31 UTCVendor advisory
  70. 2026-06-27 12:31 UTCGHSA enrichment
  71. 2026-06-27 03:08 UTCEPSS rescore
  72. 2026-06-27 00:50 UTCVendor advisory
  73. 2026-06-27 00:50 UTCGHSA enrichment
  74. 2026-06-26 12:35 UTCVendor advisory
  75. 2026-06-26 12:34 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42913?
CVE-2026-42913 is a high vulnerability published on June 9, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Remote Desktop Client allows an unauthorized attacker to execute code over a network.
When was CVE-2026-42913 disclosed?
CVE-2026-42913 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42913 actively exploited?
CVE-2026-42913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 38.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42913?
CVE-2026-42913 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42913

Explore →

Is Your Infrastructure Affected by CVE-2026-42913?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs