CVE-2026-91718

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreHIGH confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 6 sources updated this week
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: None knownExposed: 0

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

Use after free in Core in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS v3
9.6
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
9.6(high)
EG Risk
43(Track)
EG Risk 43/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
Severity96% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 15, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/553133215
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0541751186.html

Vendor Advisories for CVE-2026-91718(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 52× in last 7d / 52× 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-09-20 13:24 UTCVendor advisory
  2. 2026-09-20 13:24 UTCGHSA enrichment
  3. 2026-09-20 09:13 UTCVendor advisory
  4. 2026-09-20 09:13 UTCGHSA enrichment
  5. 2026-09-20 05:01 UTCVendor advisory
  6. 2026-09-20 05:01 UTCGHSA enrichment
  7. 2026-09-20 00:50 UTCVendor advisory
  8. 2026-09-20 00:50 UTCGHSA enrichment
  9. 2026-09-19 20:38 UTCVendor advisory
  10. 2026-09-19 20:38 UTCGHSA enrichment
  11. 2026-09-19 16:27 UTCEG score recompute
  12. 2026-09-19 16:27 UTCVendor advisory
  13. 2026-09-19 16:27 UTCGHSA enrichment
  14. 2026-09-19 12:16 UTCVendor advisory
  15. 2026-09-19 12:16 UTCGHSA enrichment
  16. 2026-09-19 08:04 UTCVendor advisory
  17. 2026-09-19 08:04 UTCGHSA enrichment
  18. 2026-09-19 03:54 UTCVendor advisory
  19. 2026-09-19 03:53 UTCGHSA enrichment
  20. 2026-09-18 23:43 UTCVendor advisory
  21. 2026-09-18 23:42 UTCGHSA enrichment
  22. 2026-09-18 19:31 UTCEG score recompute
  23. 2026-09-18 19:31 UTCGHSA enrichment
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 15:20 UTCGHSA enrichment
Show 27 more
  1. 2026-09-18 11:09 UTCGHSA enrichment
  2. 2026-09-18 06:58 UTCGHSA enrichment
  3. 2026-09-18 02:47 UTCGHSA enrichment
  4. 2026-09-17 22:36 UTCEG score recompute
  5. 2026-09-17 22:36 UTCGHSA enrichment
  6. 2026-09-17 19:32 UTCEPSS rescore
  7. 2026-09-17 18:24 UTCGHSA enrichment
  8. 2026-09-17 13:42 UTCGHSA enrichment
  9. 2026-09-17 12:55 UTCGHSA enrichment
  10. 2026-09-17 08:32 UTCGHSA enrichment
  11. 2026-09-17 04:20 UTCGHSA enrichment
  12. 2026-09-17 04:06 UTCGHSA enrichment
  13. 2026-09-17 03:48 UTCGHSA enrichment
  14. 2026-09-16 23:37 UTCGHSA enrichment
  15. 2026-09-16 19:25 UTCGHSA enrichment
  16. 2026-09-16 18:49 UTCGHSA enrichment
  17. 2026-09-16 14:38 UTCEG score recompute
  18. 2026-09-16 14:38 UTCGHSA enrichment
  19. 2026-09-16 14:09 UTCEPSS rescore
  20. 2026-09-16 10:26 UTCGHSA enrichment
  21. 2026-09-16 10:12 UTCEG score recompute▲ 0.80
  22. 2026-09-16 10:12 UTCGHSA enrichment
  23. 2026-09-16 10:11 UTCMITRE cvelistV5CVSS v3 → 9.6 · severity → CRITICAL
  24. 2026-09-16 08:56 UTCGHSA enrichment
  25. 2026-09-15 21:18 UTCNVD update
  26. 2026-09-15 20:43 UTCEG score recompute
  27. 2026-09-15 20:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-91718?
CVE-2026-91718 is a critical vulnerability published on September 15, 2026. Use after free in Core in Google Chrome prior to 153.0.8010.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
When was CVE-2026-91718 disclosed?
CVE-2026-91718 was first published in the National Vulnerability Database on September 15, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-91718 actively exploited?
CVE-2026-91718 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-91718?
CVE-2026-91718 has a CVSS v3.1 base score of 9.6 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-91718?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-91718, 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-91718

Explore →

Is Your Infrastructure Affected by CVE-2026-91718?

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

Start Free Scan →Browse All CVEs