CVE-2026-58300

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
6.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.2Exploit: NoneExposed: 0

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

Absolute path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.

CVSS v3
6.2
EG Score
6.2(high)
EG Risk
EPSS
26.1%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 22, 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-58300

Vendor Advisories for CVE-2026-58300(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 15× in last 7d / 63× 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-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 03:44 UTCEG score recompute
  9. 2026-07-19 03:44 UTCVendor advisory
  10. 2026-07-19 03:44 UTCGHSA enrichment
  11. 2026-07-19 02:29 UTCEPSS rescore
  12. 2026-07-18 10:04 UTCEPSS rescore
  13. 2026-07-16 23:35 UTCVendor advisory
  14. 2026-07-16 23:35 UTCGHSA enrichment
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-15 21:29 UTCVendor advisory
  17. 2026-07-15 21:29 UTCGHSA enrichment
  18. 2026-07-15 16:57 UTCEPSS rescore
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 02:00 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 19:24 UTCVendor advisory
  23. 2026-07-14 19:24 UTCGHSA enrichment
  24. 2026-07-13 22:31 UTCEPSS rescore
  25. 2026-07-13 17:18 UTCGHSA enrichment
Show 38 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-12 15:12 UTCVendor advisory
  4. 2026-07-12 15:12 UTCGHSA enrichment
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 13:07 UTCVendor advisory
  7. 2026-07-11 13:07 UTCGHSA enrichment
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 11:02 UTCVendor advisory
  11. 2026-07-10 11:01 UTCGHSA enrichment
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 08:55 UTCVendor advisory
  15. 2026-07-09 08:55 UTCGHSA enrichment
  16. 2026-07-08 21:10 UTCMITRE cvelistV5CVSS v3 → 6.2
  17. 2026-07-08 15:16 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-08 06:49 UTCVendor advisory
  20. 2026-07-08 06:49 UTCGHSA enrichment
  21. 2026-07-08 00:21 UTCNVD updateCVSS v3 → 5.5
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-07 04:43 UTCVendor advisory
  25. 2026-07-07 04:43 UTCGHSA enrichment
  26. 2026-07-06 16:27 UTCEPSS rescore
  27. 2026-07-06 16:27 UTCEPSS rescore
  28. 2026-07-06 02:37 UTCVendor advisory
  29. 2026-07-06 02:37 UTCGHSA enrichment
  30. 2026-07-06 02:23 UTCEPSS rescore
  31. 2026-07-06 02:23 UTCEPSS rescore
  32. 2026-07-05 02:31 UTCEPSS rescore
  33. 2026-07-05 02:30 UTCEPSS rescore
  34. 2026-07-05 00:32 UTCVendor advisory
  35. 2026-07-05 00:32 UTCGHSA enrichment
  36. 2026-07-03 22:27 UTCEG score recompute
  37. 2026-07-03 22:27 UTCVendor advisory
  38. 2026-07-03 22:27 UTCGHSA enrichment

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58300?

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