Chrome is widely deployed; this remote sandbox-escape in Payments can enable attacker-controlled code execution in many enterprise endpoints.
CVE-2026-19175
Use-after-free in Chrome Payments allows sandbox escape and possible remote code execution.
Is CVE-2026-19175 being exploited?
Not confirmed. CVE-2026-19175 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-19175?
CVE-2026-19175 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-19175?
Yes. A fix has been recorded for CVE-2026-19175. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19175 affect?
CVE-2026-19175 affects Google Chrome <151.0.7922.109 (Payments component) - desktop & mobile builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19175?
Update Chrome to 151.0.7922.109 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can craft an HTML page to escape Chrome sandbox, potentially enabling arbitrary code execution on affected hosts.
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.