CVE-2026-58293

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

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

External control of file name or path in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.

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

Published

July 3, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Jul 6, 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-58293

Vendor Advisories for CVE-2026-58293(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 17× in last 7d / 96× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 14:18 UTCEPSS rescore
  5. 2026-07-23 03:21 UTCEG score recompute
  6. 2026-07-22 14:08 UTCEPSS rescore
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-21 15:25 UTCEPSS rescore
  10. 2026-07-20 17:08 UTCEPSS rescore
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 03:44 UTCEG score recompute
  14. 2026-07-19 03:44 UTCVendor advisory
  15. 2026-07-19 03:44 UTCGHSA enrichment
  16. 2026-07-19 02:29 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 00:45 UTCVendor advisory
  19. 2026-07-17 00:45 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-16 13:28 UTCVendor advisory
  22. 2026-07-16 13:28 UTCGHSA enrichment
  23. 2026-07-16 02:15 UTCVendor advisory
  24. 2026-07-16 02:15 UTCGHSA enrichment
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 71 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 15:02 UTCVendor advisory
  3. 2026-07-15 15:02 UTCGHSA enrichment
  4. 2026-07-15 03:48 UTCVendor advisory
  5. 2026-07-15 03:48 UTCGHSA enrichment
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 02:00 UTCEPSS rescore
  8. 2026-07-14 16:36 UTCVendor advisory
  9. 2026-07-14 16:36 UTCGHSA enrichment
  10. 2026-07-14 05:23 UTCVendor advisory
  11. 2026-07-14 05:23 UTCGHSA enrichment
  12. 2026-07-13 22:31 UTCEPSS rescore
  13. 2026-07-13 18:10 UTCGHSA enrichment
  14. 2026-07-13 06:58 UTCGHSA enrichment
  15. 2026-07-13 06:13 UTCEPSS rescore
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-12 19:45 UTCVendor advisory
  18. 2026-07-12 19:45 UTCGHSA enrichment
  19. 2026-07-12 08:32 UTCVendor advisory
  20. 2026-07-12 08:32 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 21:19 UTCGHSA enrichment
  23. 2026-07-11 10:07 UTCVendor advisory
  24. 2026-07-11 10:07 UTCGHSA enrichment
  25. 2026-07-11 08:27 UTCEPSS rescore
  26. 2026-07-11 08:27 UTCEPSS rescore
  27. 2026-07-10 22:54 UTCVendor advisory
  28. 2026-07-10 22:54 UTCGHSA enrichment
  29. 2026-07-10 11:40 UTCVendor advisory
  30. 2026-07-10 11:40 UTCGHSA enrichment
  31. 2026-07-10 00:22 UTCVendor advisory
  32. 2026-07-10 00:22 UTCGHSA enrichment
  33. 2026-07-09 19:10 UTCEPSS rescore
  34. 2026-07-09 19:10 UTCEPSS rescore
  35. 2026-07-09 13:06 UTCVendor advisory
  36. 2026-07-09 13:06 UTCGHSA enrichment
  37. 2026-07-09 01:51 UTCVendor advisory
  38. 2026-07-09 01:51 UTCGHSA enrichment
  39. 2026-07-08 21:10 UTCMITRE cvelistV5CVSS v3 → 8.1
  40. 2026-07-08 15:16 UTCEPSS rescore
  41. 2026-07-08 15:16 UTCEPSS rescore
  42. 2026-07-08 14:38 UTCVendor advisory
  43. 2026-07-08 14:38 UTCGHSA enrichment
  44. 2026-07-08 03:25 UTCVendor advisory
  45. 2026-07-08 03:25 UTCGHSA enrichment
  46. 2026-07-07 16:12 UTCVendor advisory
  47. 2026-07-07 16:12 UTCGHSA enrichment
  48. 2026-07-07 14:17 UTCNVD updateCVSS v3 → 7.5
  49. 2026-07-07 04:59 UTCVendor advisory
  50. 2026-07-07 04:59 UTCGHSA enrichment
  51. 2026-07-06 17:45 UTCVendor advisory
  52. 2026-07-06 17:44 UTCGHSA enrichment
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 06:31 UTCVendor advisory
  56. 2026-07-06 06:31 UTCGHSA enrichment
  57. 2026-07-06 02:23 UTCEPSS rescore
  58. 2026-07-06 02:23 UTCEPSS rescore
  59. 2026-07-05 19:19 UTCVendor advisory
  60. 2026-07-05 19:19 UTCGHSA enrichment
  61. 2026-07-05 08:06 UTCVendor advisory
  62. 2026-07-05 08:06 UTCGHSA enrichment
  63. 2026-07-05 02:31 UTCEPSS rescore
  64. 2026-07-05 02:30 UTCEPSS rescore
  65. 2026-07-04 20:53 UTCVendor advisory
  66. 2026-07-04 20:53 UTCGHSA enrichment
  67. 2026-07-04 09:41 UTCVendor advisory
  68. 2026-07-04 09:41 UTCGHSA enrichment
  69. 2026-07-03 22:27 UTCEG score recompute
  70. 2026-07-03 22:27 UTCVendor advisory
  71. 2026-07-03 22:27 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-58293?
CVE-2026-58293 is a high vulnerability published on July 3, 2026. External control of file name or path in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
When was CVE-2026-58293 disclosed?
CVE-2026-58293 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-58293 actively exploited?
CVE-2026-58293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 35.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58293?
CVE-2026-58293 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-58293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58293, 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-58293

Explore →

Is Your Infrastructure Affected by CVE-2026-58293?

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

Start Free Scan →Browse All CVEs