CVE-2026-58299

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.5; sources differ by 0.0.

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

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

Time-of-check time-of-use (toctou) race condition in Microsoft Edge for Android allows an unauthorized attacker to execute code over a network.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
19.4%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (1)

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

Vendor Advisories for CVE-2026-58299(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 27× in last 7d / 27× 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 23:25 UTCEG score recompute
  2. 2026-07-06 23:25 UTCVendor advisory
  3. 2026-07-06 23:25 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 11:17 UTCEG score recompute
  7. 2026-07-06 11:17 UTCVendor advisory
  8. 2026-07-06 11:16 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 23:08 UTCEG score recompute
  12. 2026-07-05 23:08 UTCVendor advisory
  13. 2026-07-05 23:08 UTCGHSA enrichment
  14. 2026-07-05 10:59 UTCEG score recompute
  15. 2026-07-05 10:59 UTCVendor advisory
  16. 2026-07-05 10:59 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 22:51 UTCEG score recompute
  20. 2026-07-04 22:51 UTCVendor advisory
  21. 2026-07-04 22:51 UTCGHSA enrichment
  22. 2026-07-04 10:44 UTCEG score recompute
  23. 2026-07-04 10:44 UTCVendor advisory
  24. 2026-07-04 10:44 UTCGHSA enrichment
  25. 2026-07-03 22:27 UTCEG score recompute
Show 2 more
  1. 2026-07-03 22:27 UTCVendor advisory
  2. 2026-07-03 22:27 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-58299?
CVE-2026-58299 is a high vulnerability published on July 3, 2026. Time-of-check time-of-use (toctou) race condition in Microsoft Edge for Android allows an unauthorized attacker to execute code over a network.
When was CVE-2026-58299 disclosed?
CVE-2026-58299 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58299 actively exploited?
CVE-2026-58299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58299?
CVE-2026-58299 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-58299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58299, 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-58299

Explore →

Is Your Infrastructure Affected by CVE-2026-58299?

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

Start Free Scan →Browse All CVEs