Insufficient policy enforcement in Browser in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Low)
CVE-2026-14095
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- Vendor severity
- LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
- EG Score
- 9.6(medium)
- EG Risk
- 48(Track)EG Risk 48/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 computedSeverity96% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 1, 2026
Advisory Details (2)
Auto-updated Aug 23, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.htmlVendor Advisories for CVE-2026-14095(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 149.0.7827.53-1~deb13u1 (378 versions) | 150.0.7871.46-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb12u1 (144 versions) | 150.0.7871.46-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (145 versions) | 150.0.7871.46-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 67× in last 7d / 355× 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 560 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 04:46 UTCVendor advisory
- 2026-08-25 04:46 UTCGHSA enrichment
- 2026-08-25 00:55 UTCVendor advisory
- 2026-08-25 00:55 UTCGHSA enrichment
- 2026-08-24 21:04 UTCVendor advisory
- 2026-08-24 21:04 UTCGHSA enrichment
- 2026-08-24 15:00 UTCEG score recompute
- 2026-08-24 15:00 UTCVendor advisory
- 2026-08-24 15:00 UTCGHSA enrichment
- 2026-08-24 11:05 UTCVendor advisory
- 2026-08-24 11:05 UTCGHSA enrichment
- 2026-08-24 04:17 UTCVendor advisory
- 2026-08-24 04:17 UTCGHSA enrichment
- 2026-08-23 23:09 UTCVendor advisory
- 2026-08-23 23:09 UTCGHSA enrichment
- 2026-08-23 19:18 UTCVendor advisory
- 2026-08-23 19:18 UTCGHSA enrichment
- 2026-08-23 15:26 UTCVendor advisory
- 2026-08-23 15:26 UTCGHSA enrichment
- 2026-08-23 11:35 UTCVendor advisory
- 2026-08-23 11:35 UTCGHSA enrichment
- 2026-08-23 07:44 UTCVendor advisory
- 2026-08-23 07:44 UTCGHSA enrichment
- 2026-08-23 03:53 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-23 03:53 UTCGHSA enrichment
- 2026-08-23 00:02 UTCVendor advisory
- 2026-08-23 00:02 UTCGHSA enrichment
- 2026-08-22 20:11 UTCVendor advisory
- 2026-08-22 20:11 UTCGHSA enrichment
- 2026-08-22 15:29 UTCVendor advisory
- 2026-08-22 15:29 UTCGHSA enrichment
- 2026-08-22 11:34 UTCVendor advisory
- 2026-08-22 11:34 UTCGHSA enrichment
- 2026-08-22 07:43 UTCVendor advisory
- 2026-08-22 07:43 UTCGHSA enrichment
- 2026-08-22 01:00 UTCEG score recompute
- 2026-08-22 01:00 UTCVendor advisory
- 2026-08-22 01:00 UTCGHSA enrichment
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 21:09 UTCGHSA enrichment
- 2026-08-21 17:18 UTCGHSA enrichment
- 2026-08-21 12:24 UTCVendor advisory
- 2026-08-21 12:24 UTCGHSA enrichment
- 2026-08-21 08:33 UTCVendor advisory
- 2026-08-21 08:33 UTCGHSA enrichment
- 2026-08-21 04:42 UTCVendor advisory
- 2026-08-21 04:42 UTCGHSA enrichment
- 2026-08-21 00:38 UTCEG score recompute
- 2026-08-21 00:38 UTCVendor advisory
- 2026-08-21 00:38 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 20:46 UTCVendor advisory
- 2026-08-20 20:46 UTCGHSA enrichment
- 2026-08-20 16:55 UTCVendor advisory
- 2026-08-20 16:55 UTCGHSA enrichment
- 2026-08-20 12:41 UTCVendor advisory
- 2026-08-20 12:41 UTCGHSA enrichment
- 2026-08-20 08:49 UTCVendor advisory
- 2026-08-20 08:49 UTCGHSA enrichment
- 2026-08-20 04:58 UTCEG score recompute
- 2026-08-20 04:58 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 16:30 UTCVendor advisory
- 2026-08-19 16:30 UTCGHSA enrichment
- 2026-08-19 12:33 UTCVendor advisory
- 2026-08-19 12:33 UTCGHSA enrichment
- 2026-08-19 07:58 UTCVendor advisory
- 2026-08-19 07:58 UTCGHSA enrichment
- 2026-08-19 03:55 UTCVendor advisory
- 2026-08-19 03:55 UTCGHSA enrichment
- 2026-08-18 22:33 UTCEG score recompute
- 2026-08-18 22:33 UTCVendor advisory
- 2026-08-18 22:33 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 04:54 UTCGHSA enrichment
- 2026-08-17 23:47 UTCVendor advisory
- 2026-08-17 23:47 UTCGHSA enrichment
- 2026-08-17 15:48 UTCEG score recompute
- 2026-08-17 15:48 UTCVendor advisory
- 2026-08-17 15:48 UTCGHSA enrichment
- 2026-08-17 11:57 UTCVendor advisory
- 2026-08-17 11:57 UTCGHSA enrichment
- 2026-08-17 08:07 UTCVendor advisory
- 2026-08-17 08:07 UTCGHSA enrichment
- 2026-08-17 04:16 UTCVendor advisory
- 2026-08-17 04:16 UTCGHSA enrichment
- 2026-08-17 00:25 UTCVendor advisory
- 2026-08-17 00:25 UTCGHSA enrichment
- 2026-08-16 20:34 UTCVendor advisory
- 2026-08-16 20:34 UTCGHSA enrichment
- 2026-08-16 16:42 UTCEG score recompute
- 2026-08-16 16:42 UTCVendor advisory
- 2026-08-16 16:42 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:50 UTCVendor advisory
- 2026-08-16 12:50 UTCGHSA enrichment
- 2026-08-16 08:59 UTCVendor advisory
- 2026-08-16 08:59 UTCGHSA enrichment
- 2026-08-16 05:08 UTCEG score recompute
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-14095?
When was CVE-2026-14095 disclosed?
Is CVE-2026-14095 actively exploited?
What is the CVSS score of CVE-2026-14095?
How do I remediate CVE-2026-14095?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14095
Is Your Infrastructure Affected by CVE-2026-14095?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.