CVE-2026-66310

HIGHNVD 7.17.7
EchelonGraph scoreHIGH confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-04. NVD baseline CVSS 7.1; sources differ by 0.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.7EG
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.1Exploit: None knownExposed: 0

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

External control of file name or path in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.

CVSS v3
7.1
EG Score
7.7(high)
EG Risk
35(Track)
EG Risk 35/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
Severity77% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 20, 2026

Advisory Details (1)

Auto-updated Aug 3, 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-66310

Vendor Advisories for CVE-2026-66310(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 51× in last 7d / 135× 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 135 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-66310?
CVE-2026-66310 is a high vulnerability published on August 3, 2026. External control of file name or path in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.
When was CVE-2026-66310 disclosed?
CVE-2026-66310 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66310 actively exploited?
CVE-2026-66310 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 70.3% of all scored CVEs.
What is the CVSS score of CVE-2026-66310?
CVE-2026-66310 has a CVSS v3 base score of 7.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.7.
How do I remediate CVE-2026-66310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66310, 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-66310

Explore →

Is Your Infrastructure Affected by CVE-2026-66310?

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