Chrome is ubiquitous; a sandbox escape enabling remote arbitrary code execution on user endpoints risks widespread enterprise compromise and requires org-wide mitigation.
CVE-2026-19164
Chrome sandbox escape via crafted HTML in codecs enabling remote code execution
Is CVE-2026-19164 being exploited?
Not confirmed. CVE-2026-19164 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.36% probability of exploitation in the next 30 days.
How severe is CVE-2026-19164?
CVE-2026-19164 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-19164?
Yes. A fix has been recorded for CVE-2026-19164. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19164 affect?
CVE-2026-19164 affects Google Chrome <151.0.7922.109, Chromium-based browsers using same codecs, ChromeOS builds with same code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19164?
Update Chrome to 151.0.7922.109+ and enforce endpoint patching and EDR monitoring
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sandbox escape via crafted HTML/codec allowing arbitrary code execution on user endpoints.
Immediate action required
- affected< 151.0.7922.109
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.