Chrome is ubiquitous; a sandbox escape enabling host compromise from the browser is high-impact and relevant to all IT/endpoint teams.
CVE-2026-17672
Chromecast sandbox escape in Chrome allows renderer-compromised attacker to break out.
Is CVE-2026-17672 being exploited?
Not confirmed. CVE-2026-17672 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.48% probability of exploitation in the next 30 days.
How severe is CVE-2026-17672?
CVE-2026-17672 is rated Critical with a CVSS score of 9.6. 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-17672?
Yes. A fix has been recorded for CVE-2026-17672. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17672 affect?
CVE-2026-17672 affects Google Chrome < 151.0.7922.72, Chromium-based browsers with Chromecast feature. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17672?
Upgrade Chrome to 151.0.7922.72+ immediately; restrict access to untrusted sites until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape: attacker with a compromised renderer can execute code outside the browser sandbox, enabling host compromise and persistence.
Immediate action required
- affected< 151.0.7922.72
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.