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:github_m, 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)
EPSS
28.1%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 6, 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(1)

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.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:37 UTCEG score recompute
  4. 2026-07-06 02:37 UTCVendor advisory
  5. 2026-07-06 02:37 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-05 02:31 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-05 00:32 UTCEG score recompute
  11. 2026-07-05 00:32 UTCVendor advisory
  12. 2026-07-05 00:32 UTCGHSA enrichment
  13. 2026-07-03 22:27 UTCEG score recompute
  14. 2026-07-03 22:27 UTCVendor advisory
  15. 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 6, 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 28.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 v3 base score of 6.2 (NVD).
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.