Integer overflow 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-16416
This critical-severity CVE scores 9.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- 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.3
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.3(medium)
- EG Risk
- 42(Track)EG Risk 42/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 computedSeverity93% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
July 21, 2026
Last Modified
July 30, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0256605430.htmlVendor Advisories for CVE-2026-16416(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 48× in last 7d / 231× 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 723 total refreshes for this CVE.
- 2026-09-14 17:06 UTCVendor advisory
- 2026-09-14 17:06 UTCGHSA enrichment
- 2026-09-14 11:09 UTCVendor advisory
- 2026-09-14 11:09 UTCGHSA enrichment
- 2026-09-14 06:58 UTCVendor advisory
- 2026-09-14 06:58 UTCGHSA enrichment
- 2026-09-14 02:47 UTCVendor advisory
- 2026-09-14 02:47 UTCGHSA enrichment
- 2026-09-13 22:30 UTCVendor advisory
- 2026-09-13 22:30 UTCGHSA enrichment
- 2026-09-13 18:19 UTCEG score recompute
- 2026-09-13 18:19 UTCVendor advisory
- 2026-09-13 18:19 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 14:01 UTCVendor advisory
- 2026-09-13 14:01 UTCGHSA enrichment
- 2026-09-13 09:49 UTCVendor advisory
- 2026-09-13 09:49 UTCGHSA enrichment
- 2026-09-13 05:38 UTCVendor advisory
- 2026-09-13 05:38 UTCGHSA enrichment
- 2026-09-13 01:27 UTCVendor advisory
- 2026-09-13 01:27 UTCGHSA enrichment
- 2026-09-12 20:57 UTCVendor advisory
- 2026-09-12 20:57 UTCGHSA enrichment
- 2026-09-12 16:44 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-12 16:44 UTCVendor advisory
- 2026-09-12 16:44 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 12:32 UTCVendor advisory
- 2026-09-12 12:32 UTCGHSA enrichment
- 2026-09-12 06:54 UTCVendor advisory
- 2026-09-12 06:54 UTCGHSA enrichment
- 2026-09-12 02:20 UTCVendor advisory
- 2026-09-12 02:20 UTCGHSA enrichment
- 2026-09-11 22:06 UTCVendor advisory
- 2026-09-11 22:06 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-11 07:30 UTCGHSA enrichment
- 2026-09-11 03:19 UTCGHSA enrichment
- 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
- 2026-09-09 09:21 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 01:56 UTCVendor advisory
- 2026-09-08 01:56 UTCGHSA enrichment
- 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 17:30 UTCEG score recompute
- 2026-09-06 17:30 UTCVendor advisory
- 2026-09-06 17:30 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 12:58 UTCVendor advisory
- 2026-09-06 12:58 UTCGHSA enrichment
- 2026-09-06 08:47 UTCVendor advisory
- 2026-09-06 08:47 UTCGHSA enrichment
- 2026-09-06 03:58 UTCVendor advisory
- 2026-09-06 03:58 UTCGHSA enrichment
- 2026-09-05 23:46 UTCVendor advisory
- 2026-09-05 23:46 UTCGHSA enrichment
- 2026-09-05 19:36 UTCEG score recompute
- 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 07:56 UTCVendor advisory
- 2026-08-31 07:56 UTCGHSA enrichment
- 2026-08-31 03:18 UTCVendor advisory
- 2026-08-31 03:18 UTCGHSA enrichment
- 2026-08-30 23:06 UTCEG score recompute
- 2026-08-30 23:06 UTCVendor advisory
- 2026-08-30 23:06 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 18:53 UTCVendor advisory
- 2026-08-30 18:53 UTCGHSA enrichment
- 2026-08-30 14:42 UTCVendor advisory
- 2026-08-30 14:42 UTCGHSA enrichment
- 2026-08-30 10:27 UTCVendor advisory
- 2026-08-30 10:27 UTCGHSA enrichment
- 2026-08-30 05:11 UTCEG score recompute
- 2026-08-30 05:11 UTCVendor advisory
- 2026-08-30 05:11 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-16416?
When was CVE-2026-16416 disclosed?
Is CVE-2026-16416 actively exploited?
What is the CVSS score of CVE-2026-16416?
How do I remediate CVE-2026-16416?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16416
Is Your Infrastructure Affected by CVE-2026-16416?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.