Insufficient validation of untrusted input in Chromecast in Google Chrome prior to 150.0.7871.182 allowed a local attacker to potentially perform a sandbox escape via malicious network traffic. (Chromium security severity: High)
CVE-2026-16414
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-22. NVD baseline CVSS 7.8; 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
- 7.8
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 7.8(medium)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Jul 24, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0256605430.htmlVendor Advisories for CVE-2026-16414(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 ... 150.0.7871.46-1~deb13u1 (390 versions) | 150.0.7871.181-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (156 versions) | 150.0.7871.181-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (157 versions) | 150.0.7871.181-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 26× in last 7d / 125× 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 439 total refreshes for this CVE.
- 2026-09-14 17:06 UTCVendor advisory
- 2026-09-14 17:06 UTCGHSA enrichment
- 2026-09-14 05:13 UTCVendor advisory
- 2026-09-14 05:13 UTCGHSA enrichment
- 2026-09-13 17:26 UTCEG score recompute
- 2026-09-13 17:26 UTCVendor advisory
- 2026-09-13 17:26 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 05:38 UTCVendor advisory
- 2026-09-13 05:38 UTCGHSA enrichment
- 2026-09-12 17:50 UTCEG score recompute
- 2026-09-12 17:50 UTCVendor advisory
- 2026-09-12 17:50 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 05:43 UTCVendor advisory
- 2026-09-12 05:43 UTCGHSA enrichment
- 2026-09-11 17:54 UTCEG score recompute
- 2026-09-11 17:54 UTCVendor advisory
- 2026-09-11 17:54 UTCGHSA enrichment
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 22:06 UTCEG score recompute
- 2026-09-10 22:06 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-09 09:21 UTCEG score recompute
- 2026-09-09 09:21 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-09 09:21 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 21:44 UTCEG score recompute
- 2026-09-07 21:44 UTCVendor advisory
- 2026-09-07 21:44 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 08:47 UTCVendor advisory
- 2026-09-06 08:47 UTCGHSA enrichment
- 2026-09-05 19:36 UTCVendor advisory
- 2026-09-05 19:36 UTCGHSA enrichment
- 2026-09-05 07:18 UTCVendor advisory
- 2026-09-05 07:18 UTCGHSA enrichment
- 2026-09-04 14:17 UTCEG score recompute
- 2026-09-04 14:17 UTCVendor advisory
- 2026-09-04 14:17 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 23:43 UTCEG score recompute
- 2026-09-01 23:43 UTCVendor advisory
- 2026-09-01 23:43 UTCGHSA enrichment
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 00:43 UTCEG score recompute
- 2026-08-31 00:43 UTCVendor advisory
- 2026-08-31 00:43 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 12:55 UTCEG score recompute
- 2026-08-30 12:55 UTCVendor advisory
- 2026-08-30 12:55 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:59 UTCEG score recompute
- 2026-08-30 00:59 UTCVendor advisory
- 2026-08-30 00:59 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 22:08 UTCEG score recompute
- 2026-08-27 22:08 UTCVendor advisory
- 2026-08-27 22:08 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 10:20 UTCVendor advisory
- 2026-08-27 10:20 UTCGHSA enrichment
- 2026-08-26 22:32 UTCEG score recompute
- 2026-08-26 22:32 UTCVendor advisory
- 2026-08-26 22:32 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 10:43 UTCVendor advisory
- 2026-08-26 10:43 UTCGHSA enrichment
- 2026-08-25 22:21 UTCEG score recompute
- 2026-08-25 22:21 UTCVendor advisory
- 2026-08-25 22:20 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 10:26 UTCVendor advisory
- 2026-08-25 10:26 UTCGHSA enrichment
- 2026-08-24 22:38 UTCEG score recompute
- 2026-08-24 22:38 UTCVendor advisory
- 2026-08-24 22:38 UTCGHSA enrichment
- 2026-08-24 10:50 UTCEG score recompute
- 2026-08-24 10:50 UTCVendor advisory
- 2026-08-24 10:50 UTCGHSA enrichment
- 2026-08-23 23:02 UTCVendor advisory
- 2026-08-23 23:02 UTCGHSA enrichment
- 2026-08-23 11:13 UTCEG score recompute
- 2026-08-23 11:13 UTCVendor advisory
- 2026-08-23 11:13 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 23:26 UTCVendor advisory
- 2026-08-22 23:26 UTCGHSA enrichment
- 2026-08-22 11:38 UTCVendor advisory
- 2026-08-22 11:38 UTCGHSA enrichment
- 2026-08-21 23:50 UTCEG score recompute
- 2026-08-21 23:50 UTCVendor advisory
- 2026-08-21 23:50 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 12:02 UTCEG score recompute
- 2026-08-21 12:02 UTCVendor advisory
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-16414?
When was CVE-2026-16414 disclosed?
Is CVE-2026-16414 actively exploited?
What is the CVSS score of CVE-2026-16414?
How do I remediate CVE-2026-16414?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16414
Is Your Infrastructure Affected by CVE-2026-16414?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.