Insufficient policy enforcement in DevTools 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: Medium)
CVE-2026-13909
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
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- 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
- 28%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
July 2, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.htmlVendor Advisories for CVE-2026-13909(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(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 107× 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 597 total refreshes for this CVE.
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 10:51 UTCVendor advisory
- 2026-09-18 10:51 UTCGHSA enrichment
- 2026-09-18 06:44 UTCEG score recompute
- 2026-09-18 06:44 UTCVendor advisory
- 2026-09-18 06:44 UTCGHSA enrichment
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-14 08:38 UTCVendor advisory
- 2026-09-14 08:38 UTCGHSA enrichment
- 2026-09-14 04:39 UTCVendor advisory
- 2026-09-14 04:39 UTCGHSA enrichment
- 2026-09-14 00:41 UTCEG score recompute
- 2026-09-14 00:41 UTCVendor advisory
- 2026-09-14 00:41 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 13:10 UTCVendor advisory
- 2026-09-13 13:10 UTCGHSA enrichment
- 2026-09-13 09:12 UTCEG score recompute
- 2026-09-13 09:12 UTCVendor advisory
- 2026-09-13 09:12 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 14:58 UTCEG score recompute
- 2026-09-12 14:58 UTCVendor advisory
- 2026-09-12 14:58 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 14:30 UTCEG score recompute
- 2026-09-06 14:30 UTCVendor advisory
- 2026-09-06 14:30 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 02:23 UTCVendor advisory
- 2026-08-31 02:23 UTCGHSA enrichment
- 2026-08-30 22:20 UTCEG score recompute
- 2026-08-30 22:20 UTCVendor advisory
- 2026-08-30 22:20 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 17:34 UTCEG score recompute
- 2026-08-30 17:34 UTCVendor advisory
- 2026-08-30 17:34 UTCGHSA enrichment
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 02:49 UTCVendor advisory
- 2026-08-28 02:48 UTCGHSA enrichment
- 2026-08-27 22:36 UTCEG score recompute
- 2026-08-27 22:36 UTCVendor advisory
- 2026-08-27 22:36 UTCGHSA enrichment
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 05:02 UTCVendor advisory
- 2026-08-25 05:02 UTCGHSA enrichment
- 2026-08-25 01:03 UTCVendor advisory
- 2026-08-25 01:03 UTCGHSA enrichment
- 2026-08-24 21:05 UTCVendor advisory
- 2026-08-24 21:05 UTCGHSA enrichment
- 2026-08-24 15:14 UTCEG score recompute
- 2026-08-24 15:14 UTCVendor advisory
- 2026-08-24 15:14 UTCGHSA enrichment
- 2026-08-24 11:15 UTCEG score recompute
- 2026-08-24 11:15 UTCVendor advisory
- 2026-08-24 11:15 UTCGHSA enrichment
- 2026-08-24 04:41 UTCVendor advisory
- 2026-08-24 04:41 UTCGHSA enrichment
- 2026-08-24 00:43 UTCVendor advisory
- 2026-08-24 00:43 UTCGHSA enrichment
- 2026-08-23 20:45 UTCVendor advisory
- 2026-08-23 20:45 UTCGHSA enrichment
- 2026-08-23 16:47 UTCVendor advisory
- 2026-08-23 16:47 UTCGHSA enrichment
- 2026-08-23 12:49 UTCVendor advisory
- 2026-08-23 12:49 UTCGHSA enrichment
- 2026-08-23 08:51 UTCVendor advisory
- 2026-08-23 08:51 UTCGHSA enrichment
- 2026-08-23 04:43 UTCVendor advisory
- 2026-08-23 04:43 UTCGHSA enrichment
- 2026-08-23 00:43 UTCEG score recompute
- 2026-08-23 00:43 UTCVendor advisory
- 2026-08-23 00:43 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 20:19 UTCVendor advisory
- 2026-08-22 20:19 UTCGHSA enrichment
- 2026-08-22 12:30 UTCVendor advisory
- 2026-08-22 12:30 UTCGHSA enrichment
- 2026-08-22 07:57 UTCVendor advisory
- 2026-08-22 07:57 UTCGHSA enrichment
- 2026-08-22 01:17 UTCEG score recompute
- 2026-08-22 01:17 UTCVendor advisory
- 2026-08-22 01:17 UTCGHSA enrichment
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 21:17 UTCGHSA enrichment
- 2026-08-21 17:19 UTCGHSA enrichment
- 2026-08-21 12:42 UTCVendor advisory
- 2026-08-21 12:42 UTCGHSA enrichment
- 2026-08-21 08:42 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-693
- CVE-2021-32835EG 9.9EPSS p91CRITICAL
- CVE-2019-10328EG 9.9CRITICAL
- CVE-2019-1003030EG 9.9 KEVEPSS p100CRITICAL
- CVE-2021-27497NVD 6.5EG 9.8CRITICAL
- CVE-2020-10887EG 9.8EPSS p91CRITICAL
- CVE-2017-3197EG 9.8EPSS p93CRITICAL
- CVE-2018-9318EG 9.8EPSS p91CRITICAL
- CVE-2018-9311EG 9.8EPSS p90CRITICAL
- CVE-2017-8864EG 9.8CRITICAL
- CVE-2013-2465EG 9.8 KEVEPSS p100CRITICAL
Frequently asked(5)
What is CVE-2026-13909?
When was CVE-2026-13909 disclosed?
Is CVE-2026-13909 actively exploited?
What is the CVSS score of CVE-2026-13909?
How do I remediate CVE-2026-13909?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-13909
Is Your Infrastructure Affected by CVE-2026-13909?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.