Chrome is a widely used browser; this sandbox-escape in Windows can enable host code execution from a compromised renderer, posing broad enterprise risk.
CVE-2026-19163
Use-after-free in Chrome on Windows enabling sandbox escape via crafted HTML.
Is CVE-2026-19163 being exploited?
Not confirmed. CVE-2026-19163 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-19163?
CVE-2026-19163 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-19163?
Yes. A fix has been recorded for CVE-2026-19163. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19163 affect?
CVE-2026-19163 affects Google Chrome on Windows < 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-19163?
Update Chrome to 151.0.7922.109+ and enforce auto-updates/telemetry.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free in renderer can lead to sandbox escape and remote code execution on the host via a crafted HTML page.
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.