CVE-2026-58299

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
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)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
18.9%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 22, 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(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 / 88× 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-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:21 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 03:43 UTCEG score recompute
  10. 2026-07-19 03:43 UTCVendor advisory
  11. 2026-07-19 03:43 UTCGHSA enrichment
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-17 02:12 UTCVendor advisory
  15. 2026-07-17 02:11 UTCGHSA enrichment
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 14:02 UTCGHSA enrichment
  18. 2026-07-16 01:47 UTCVendor advisory
  19. 2026-07-16 01:47 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 13:39 UTCVendor advisory
  23. 2026-07-15 13:39 UTCGHSA enrichment
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 63 more
  1. 2026-07-15 01:30 UTCGHSA enrichment
  2. 2026-07-14 13:22 UTCVendor advisory
  3. 2026-07-14 13:22 UTCGHSA enrichment
  4. 2026-07-14 01:15 UTCVendor advisory
  5. 2026-07-14 01:15 UTCGHSA enrichment
  6. 2026-07-13 22:31 UTCEPSS rescore
  7. 2026-07-13 13:07 UTCGHSA enrichment
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 00:59 UTCVendor advisory
  11. 2026-07-13 00:59 UTCGHSA enrichment
  12. 2026-07-12 12:52 UTCVendor advisory
  13. 2026-07-12 12:52 UTCGHSA enrichment
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 00:44 UTCVendor advisory
  16. 2026-07-12 00:44 UTCGHSA enrichment
  17. 2026-07-11 12:36 UTCVendor advisory
  18. 2026-07-11 12:36 UTCGHSA enrichment
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 00:28 UTCVendor advisory
  22. 2026-07-11 00:28 UTCGHSA enrichment
  23. 2026-07-10 12:21 UTCVendor advisory
  24. 2026-07-10 12:21 UTCGHSA enrichment
  25. 2026-07-10 00:12 UTCVendor advisory
  26. 2026-07-10 00:12 UTCGHSA enrichment
  27. 2026-07-09 19:10 UTCEPSS rescore
  28. 2026-07-09 19:10 UTCEPSS rescore
  29. 2026-07-09 12:05 UTCVendor advisory
  30. 2026-07-09 12:05 UTCGHSA enrichment
  31. 2026-07-08 23:58 UTCVendor advisory
  32. 2026-07-08 23:58 UTCGHSA enrichment
  33. 2026-07-08 15:16 UTCEPSS rescore
  34. 2026-07-08 15:16 UTCEPSS rescore
  35. 2026-07-08 11:51 UTCVendor advisory
  36. 2026-07-08 11:50 UTCGHSA enrichment
  37. 2026-07-07 23:39 UTCVendor advisory
  38. 2026-07-07 23:39 UTCGHSA enrichment
  39. 2026-07-07 13:46 UTCEPSS rescore
  40. 2026-07-07 13:46 UTCEPSS rescore
  41. 2026-07-07 11:32 UTCVendor advisory
  42. 2026-07-07 11:32 UTCGHSA enrichment
  43. 2026-07-06 23:25 UTCVendor advisory
  44. 2026-07-06 23:25 UTCGHSA enrichment
  45. 2026-07-06 16:27 UTCEPSS rescore
  46. 2026-07-06 16:27 UTCEPSS rescore
  47. 2026-07-06 11:17 UTCVendor advisory
  48. 2026-07-06 11:16 UTCGHSA enrichment
  49. 2026-07-06 02:23 UTCEPSS rescore
  50. 2026-07-06 02:23 UTCEPSS rescore
  51. 2026-07-05 23:08 UTCVendor advisory
  52. 2026-07-05 23:08 UTCGHSA enrichment
  53. 2026-07-05 10:59 UTCVendor advisory
  54. 2026-07-05 10:59 UTCGHSA enrichment
  55. 2026-07-05 02:31 UTCEPSS rescore
  56. 2026-07-05 02:30 UTCEPSS rescore
  57. 2026-07-04 22:51 UTCVendor advisory
  58. 2026-07-04 22:51 UTCGHSA enrichment
  59. 2026-07-04 10:44 UTCVendor advisory
  60. 2026-07-04 10:44 UTCGHSA enrichment
  61. 2026-07-03 22:27 UTCEG score recompute
  62. 2026-07-03 22:27 UTCVendor advisory
  63. 2026-07-03 22:27 UTCGHSA enrichment

Related CVEs(same vendor + same CWE)

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 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-58299 actively exploited?
CVE-2026-58299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 18.9% 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 v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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