CVE-2026-55945

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreHIGH confidence

Score 4.2 from GitHub Security Advisory published 2026-07-03. the CNA's CVSS baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
4.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.2Exploit: 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 Microsoft Edge (Chromium-based) allows an authorized attacker to disclose information locally.

CVSS v3
4.2
EG Score
4.2(high)
EG Risk
19(Track)
EG Risk 19/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
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
4.2%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 8, 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-55945

Vendor Advisories for CVE-2026-55945(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 70× 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.

  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:20 UTCEG score recompute
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 03:49 UTCEG score recompute
  11. 2026-07-19 03:49 UTCVendor advisory
  12. 2026-07-19 03:48 UTCGHSA enrichment
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-17 13:54 UTCEG score recompute
  16. 2026-07-17 13:54 UTCVendor advisory
  17. 2026-07-17 13:54 UTCGHSA enrichment
  18. 2026-07-16 17:03 UTCEPSS rescore
  19. 2026-07-16 14:53 UTCVendor advisory
  20. 2026-07-16 14:53 UTCGHSA enrichment
  21. 2026-07-15 17:08 UTCVendor advisory
  22. 2026-07-15 17:08 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 45 more
  1. 2026-07-15 02:00 UTCEPSS rescore
  2. 2026-07-14 19:24 UTCVendor advisory
  3. 2026-07-14 19:24 UTCGHSA enrichment
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 21:38 UTCGHSA enrichment
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 23:54 UTCVendor advisory
  9. 2026-07-12 23:54 UTCGHSA enrichment
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 02:10 UTCVendor advisory
  12. 2026-07-12 02:10 UTCGHSA enrichment
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 04:26 UTCVendor advisory
  16. 2026-07-11 04:26 UTCGHSA enrichment
  17. 2026-07-10 06:41 UTCVendor advisory
  18. 2026-07-10 06:41 UTCGHSA enrichment
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 19:10 UTCEPSS rescore
  21. 2026-07-09 08:58 UTCVendor advisory
  22. 2026-07-09 08:57 UTCGHSA enrichment
  23. 2026-07-08 15:16 UTCEPSS rescore
  24. 2026-07-08 15:16 UTCEPSS rescore
  25. 2026-07-08 11:13 UTCVendor advisory
  26. 2026-07-08 11:13 UTCGHSA enrichment
  27. 2026-07-07 13:46 UTCEPSS rescore
  28. 2026-07-07 13:46 UTCEPSS rescore
  29. 2026-07-07 13:28 UTCVendor advisory
  30. 2026-07-07 13:28 UTCGHSA enrichment
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 15:43 UTCVendor advisory
  34. 2026-07-06 15:43 UTCGHSA enrichment
  35. 2026-07-06 02:23 UTCEPSS rescore
  36. 2026-07-06 02:23 UTCEPSS rescore
  37. 2026-07-05 17:58 UTCVendor advisory
  38. 2026-07-05 17:58 UTCGHSA enrichment
  39. 2026-07-05 02:31 UTCEPSS rescore
  40. 2026-07-05 02:30 UTCEPSS rescore
  41. 2026-07-04 20:14 UTCVendor advisory
  42. 2026-07-04 20:14 UTCGHSA enrichment
  43. 2026-07-03 22:29 UTCEG score recompute
  44. 2026-07-03 22:29 UTCVendor advisory
  45. 2026-07-03 22:29 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-55945?
CVE-2026-55945 is a medium vulnerability published on July 3, 2026. Concurrent execution using shared resource with improper synchronization ('race condition') in Microsoft Edge (Chromium-based) allows an authorized attacker to disclose information locally.
When was CVE-2026-55945 disclosed?
CVE-2026-55945 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55945 actively exploited?
CVE-2026-55945 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55945?
CVE-2026-55945 has a CVSS v4.0 base score of 4.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-55945?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55945, 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-55945

Explore →

Is Your Infrastructure Affected by CVE-2026-55945?

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

Start Free Scan →Browse All CVEs