CVE-2026-66313

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-08-04. the CNA's CVSS baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

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

Origin validation error in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform tampering locally.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
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-66313

Vendor Advisories for CVE-2026-66313(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 34× in last 7d / 74× 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-08-20 17:07 UTCEG score recompute
  2. 2026-08-20 17:07 UTCVendor advisory
  3. 2026-08-20 17:07 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 16:57 UTCVendor advisory
  6. 2026-08-19 16:57 UTCGHSA enrichment
  7. 2026-08-19 15:49 UTCVendor advisory
  8. 2026-08-19 15:49 UTCGHSA enrichment
  9. 2026-08-18 17:33 UTCVendor advisory
  10. 2026-08-18 17:33 UTCGHSA enrichment
  11. 2026-08-18 16:00 UTCEG score recompute
  12. 2026-08-18 16:00 UTCVendor advisory
  13. 2026-08-18 16:00 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 18:25 UTCEG score recompute
  16. 2026-08-17 18:25 UTCVendor advisory
  17. 2026-08-17 18:25 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-16 21:04 UTCEG score recompute
  20. 2026-08-16 21:04 UTCVendor advisory
  21. 2026-08-16 21:04 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-15 19:20 UTCEG score recompute
  24. 2026-08-15 19:20 UTCVendor advisory
  25. 2026-08-15 19:20 UTCGHSA enrichment
Show 49 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 17:36 UTCVendor advisory
  3. 2026-08-14 17:36 UTCGHSA enrichment
  4. 2026-08-14 17:11 UTCVendor advisory
  5. 2026-08-14 17:11 UTCGHSA enrichment
  6. 2026-08-13 22:54 UTCEG score recompute
  7. 2026-08-13 22:54 UTCVendor advisory
  8. 2026-08-13 22:54 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-12 21:10 UTCEG score recompute
  11. 2026-08-12 21:10 UTCGHSA enrichment
  12. 2026-08-12 13:51 UTCEPSS rescore
  13. 2026-08-11 19:19 UTCEG score recompute
  14. 2026-08-11 19:19 UTCVendor advisory
  15. 2026-08-11 19:19 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 17:35 UTCGHSA enrichment
  18. 2026-08-09 21:57 UTCEG score recompute
  19. 2026-08-09 21:57 UTCGHSA enrichment
  20. 2026-08-09 13:47 UTCEPSS rescore
  21. 2026-08-08 20:14 UTCEG score recompute
  22. 2026-08-08 20:14 UTCVendor advisory
  23. 2026-08-08 20:14 UTCGHSA enrichment
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-07 18:29 UTCEG score recompute
  26. 2026-08-07 18:29 UTCGHSA enrichment
  27. 2026-08-06 22:25 UTCEG score recompute
  28. 2026-08-06 22:25 UTCVendor advisory
  29. 2026-08-06 22:25 UTCGHSA enrichment
  30. 2026-08-06 17:17 UTCVendor advisory
  31. 2026-08-06 17:16 UTCGHSA enrichment
  32. 2026-08-06 15:50 UTCEG score recompute
  33. 2026-08-06 15:50 UTCVendor advisory
  34. 2026-08-06 15:50 UTCGHSA enrichment
  35. 2026-08-06 13:47 UTCEPSS rescore
  36. 2026-08-05 19:17 UTCEPSS rescore
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 18:18 UTCGHSA enrichment
  39. 2026-08-04 16:34 UTCEG score recompute
  40. 2026-08-04 16:34 UTCVendor advisory
  41. 2026-08-04 16:34 UTCGHSA enrichment
  42. 2026-08-04 15:38 UTCEG score recompute
  43. 2026-08-04 15:38 UTCVendor advisory
  44. 2026-08-04 15:38 UTCGHSA enrichment
  45. 2026-08-04 15:10 UTCEPSS rescore
  46. 2026-08-04 00:25 UTCEG score recompute
  47. 2026-08-04 00:25 UTCVendor advisory
  48. 2026-08-03 23:20 UTCEG score recompute
  49. 2026-08-03 23:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66313?
CVE-2026-66313 is a medium vulnerability published on August 3, 2026. Origin validation error in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform tampering locally.
When was CVE-2026-66313 disclosed?
CVE-2026-66313 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-66313 actively exploited?
CVE-2026-66313 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-66313?
CVE-2026-66313 has a CVSS v4.0 base score of 6.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-66313?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66313, 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-66313

Explore →

Is Your Infrastructure Affected by CVE-2026-66313?

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

Start Free Scan →Browse All CVEs