Use after free in Browser in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)
CVE-2026-95298
HIGHPre-NVD 7.87.8—Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.8
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.2%
- EPSS %ILE
- 5th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
September 29, 2026
Last Modified
September 30, 2026
Advisory Details (2)
Auto-updated Sep 29, 2026🔬 Proof of concept available. No patch confirmed yet.
generic
Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0856730748.htmlVendor Advisories for CVE-2026-95298(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 154.0.8037.57-1~deb13u1 (427 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 154.0.8037.57-1~deb12u1 (191 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 154.0.8037.57-1~deb13u1 (192 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 28× 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.
- 2026-10-04 23:23 UTCEPSS rescore
- 2026-10-04 22:12 UTCGHSA enrichment
- 2026-10-04 09:57 UTCGHSA enrichment
- 2026-10-03 21:41 UTCEG score recompute
- 2026-10-03 21:41 UTCGHSA enrichment
- 2026-10-03 14:26 UTCEPSS rescore
- 2026-10-03 09:25 UTCGHSA enrichment
- 2026-10-02 21:09 UTCEG score recompute
- 2026-10-02 21:09 UTCGHSA enrichment
- 2026-10-02 17:57 UTCEPSS rescore
- 2026-10-02 08:51 UTCGHSA enrichment
- 2026-10-01 20:33 UTCEG score recompute
- 2026-10-01 20:33 UTCGHSA enrichment
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-10-01 08:17 UTCGHSA enrichment
- 2026-09-30 20:02 UTCEG score recompute
- 2026-09-30 20:01 UTCGHSA enrichment
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-30 08:47 UTCGHSA enrichment
- 2026-09-30 04:07 UTCEG score recompute
- 2026-09-30 04:07 UTCGHSA enrichment
- 2026-09-29 20:28 UTCEG score recompute▼ 1.00
- 2026-09-29 20:28 UTCGHSA enrichment
- 2026-09-29 20:22 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
- 2026-09-29 19:04 UTCGHSA enrichment
Show 3 moreShow fewer
- 2026-09-29 18:25 UTCNVD update
- 2026-09-29 17:44 UTCEG score recompute
- 2026-09-29 17:38 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-95298?
CVE-2026-95298 is a high vulnerability published on September 29, 2026. Use after free in Browser in Google Chrome prior to 154.0.8037.57 allowed a local attacker to potentially execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)
When was CVE-2026-95298 disclosed?
CVE-2026-95298 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-95298 actively exploited?
CVE-2026-95298 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95298?
CVE-2026-95298 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-95298?
No fix for CVE-2026-95298 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-95298 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-95298
Is Your Infrastructure Affected by CVE-2026-95298?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.