Chrome is widely used; a renderer-to-sandbox escape on Linux can lead to widespread endpoint compromise and requires organization-wide mitigation.
CVE-2026-19148
Out-of-bounds write in Chrome GPU on Linux enabling sandbox escape.
Is CVE-2026-19148 being exploited?
Not confirmed. CVE-2026-19148 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-19148?
CVE-2026-19148 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-19148?
Yes. A fix has been recorded for CVE-2026-19148. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19148 affect?
CVE-2026-19148 affects Google Chrome (Linux) < 151.0.7922.109. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19148?
Update Chrome on Linux to 151.0.7922.109 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Allows sandbox escape from the renderer on Linux, enabling arbitrary code execution on the host via crafted HTML.
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.