CVE-2026-58299

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 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(medium)
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 PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 3, 2026

Last Modified

September 9, 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 18× in last 7d / 125× 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 331 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-09 22:57 UTCGHSA enrichment
  4. 2026-09-08 22:53 UTCEG score recompute
  5. 2026-09-08 22:53 UTCVendor advisory
  6. 2026-09-08 22:53 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 14:16 UTCEG score recompute
  10. 2026-09-06 14:16 UTCVendor advisory
  11. 2026-09-06 14:16 UTCGHSA enrichment
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-05 23:38 UTCEG score recompute
  14. 2026-09-05 23:38 UTCVendor advisory
  15. 2026-09-05 23:38 UTCGHSA enrichment
  16. 2026-09-04 23:24 UTCEG score recompute
  17. 2026-09-04 23:24 UTCVendor advisory
  18. 2026-09-04 23:24 UTCGHSA enrichment
  19. 2026-09-04 05:07 UTCEPSS rescore
  20. 2026-09-02 19:57 UTCEG score recompute
  21. 2026-09-02 19:57 UTCVendor advisory
  22. 2026-09-02 19:57 UTCGHSA enrichment
  23. 2026-09-02 14:12 UTCEPSS rescore
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
Show 75 more
  1. 2026-08-31 16:17 UTCVendor advisory
  2. 2026-08-31 16:16 UTCGHSA enrichment
  3. 2026-08-30 23:27 UTCEG score recompute
  4. 2026-08-30 23:27 UTCVendor advisory
  5. 2026-08-30 23:27 UTCGHSA enrichment
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 11:16 UTCEG score recompute
  8. 2026-08-30 11:16 UTCVendor advisory
  9. 2026-08-30 11:16 UTCGHSA enrichment
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 23:40 UTCEG score recompute
  12. 2026-08-28 23:40 UTCVendor advisory
  13. 2026-08-28 23:40 UTCGHSA enrichment
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-27 22:09 UTCEG score recompute
  16. 2026-08-27 22:09 UTCVendor advisory
  17. 2026-08-27 22:09 UTCGHSA enrichment
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 02:53 UTCEG score recompute
  20. 2026-08-27 02:53 UTCVendor advisory
  21. 2026-08-27 02:53 UTCGHSA enrichment
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-26 14:29 UTCEG score recompute
  24. 2026-08-26 14:29 UTCGHSA enrichment
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-25 13:35 UTCVendor advisory
  27. 2026-08-25 13:35 UTCGHSA enrichment
  28. 2026-08-24 21:27 UTCVendor advisory
  29. 2026-08-24 21:27 UTCGHSA enrichment
  30. 2026-08-24 20:51 UTCEG score recompute
  31. 2026-08-24 20:51 UTCVendor advisory
  32. 2026-08-24 20:51 UTCGHSA enrichment
  33. 2026-08-24 06:58 UTCVendor advisory
  34. 2026-08-24 06:58 UTCGHSA enrichment
  35. 2026-08-23 18:50 UTCVendor advisory
  36. 2026-08-23 18:50 UTCGHSA enrichment
  37. 2026-08-23 06:43 UTCEG score recompute
  38. 2026-08-23 06:43 UTCVendor advisory
  39. 2026-08-23 06:43 UTCGHSA enrichment
  40. 2026-08-23 00:19 UTCEPSS rescore
  41. 2026-08-22 18:35 UTCVendor advisory
  42. 2026-08-22 18:35 UTCGHSA enrichment
  43. 2026-08-22 05:52 UTCEG score recompute
  44. 2026-08-22 05:52 UTCVendor advisory
  45. 2026-08-22 05:52 UTCGHSA enrichment
  46. 2026-08-21 23:49 UTCEPSS rescore
  47. 2026-08-21 17:36 UTCGHSA enrichment
  48. 2026-08-21 05:29 UTCEG score recompute
  49. 2026-08-21 05:29 UTCVendor advisory
  50. 2026-08-21 05:29 UTCGHSA enrichment
  51. 2026-08-20 22:55 UTCEPSS rescore
  52. 2026-08-20 17:22 UTCVendor advisory
  53. 2026-08-20 17:22 UTCGHSA enrichment
  54. 2026-08-20 05:21 UTCGHSA enrichment
  55. 2026-08-19 17:13 UTCEG score recompute
  56. 2026-08-19 17:13 UTCVendor advisory
  57. 2026-08-19 17:13 UTCGHSA enrichment
  58. 2026-08-19 17:04 UTCEPSS rescore
  59. 2026-08-19 16:11 UTCVendor advisory
  60. 2026-08-19 16:11 UTCGHSA enrichment
  61. 2026-08-19 06:54 UTCVendor advisory
  62. 2026-08-19 06:54 UTCGHSA enrichment
  63. 2026-08-18 17:48 UTCVendor advisory
  64. 2026-08-18 17:47 UTCGHSA enrichment
  65. 2026-08-18 16:57 UTCEG score recompute
  66. 2026-08-18 16:57 UTCVendor advisory
  67. 2026-08-18 16:57 UTCGHSA enrichment
  68. 2026-08-18 13:48 UTCEPSS rescore
  69. 2026-08-18 07:21 UTCGHSA enrichment
  70. 2026-08-17 18:51 UTCEG score recompute
  71. 2026-08-17 18:51 UTCVendor advisory
  72. 2026-08-17 18:51 UTCGHSA enrichment
  73. 2026-08-17 13:47 UTCEPSS rescore
  74. 2026-08-17 06:36 UTCVendor advisory
  75. 2026-08-17 06:36 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 September 9, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 61.0% of all scored CVEs.
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.