Chrome is widely deployed; a sandbox escape in Chrome's ANGLE can enable remote code execution across enterprises and affects many users.
CVE-2026-17717
Integer overflow in Chrome ANGLE enables sandbox escape via crafted HTML.
Is CVE-2026-17717 being exploited?
Not confirmed. CVE-2026-17717 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.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-17717?
CVE-2026-17717 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-17717?
Yes. A fix has been recorded for CVE-2026-17717. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17717 affect?
CVE-2026-17717 affects Google Chrome <151.0.7922.72, Chromium-based browsers. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17717?
Update Chrome to 151.0.7922.72+ immediately; restrict untrusted HTML and monitor endpoints.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sandbox escape via crafted HTML allowing potential arbitrary code execution outside the browser sandbox.
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.