CVE-2026-16416
Integer overflow in Chrome Chromecast may allow sandbox escape.
Is CVE-2026-16416 being exploited?
Not confirmed. CVE-2026-16416 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-16416?
CVE-2026-16416 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16416?
Yes. A fix has been recorded for CVE-2026-16416. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16416 affect?
CVE-2026-16416 affects Google Chrome <150.0.7871.182, Chromecast component within Chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16416?
Update Chrome to 150.0.7871.182 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can send crafted network traffic to trigger an integer overflow in Chromecast, escape the Chrome sandbox and achieve code execution at user level.
Patch when possible
- affected< 150.0.7871.182
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.