CVE-2026-58300

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM 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.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 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(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 3, 2026

Last Modified

August 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-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 23× in last 7d / 118× 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 196 total refreshes for this CVE.

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

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 August 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-58300 actively exploited?
CVE-2026-58300 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.1% of all scored CVEs.
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.

Start Free Scan →Browse All CVEs