Chrome on Android is widely deployed; sandbox escape enabling code execution on many devices is high-impact and newsworthy.
CVE-2026-17940
Chrome for Android PiP input validation can allow sandbox escape via crafted HTML.
Is CVE-2026-17940 being exploited?
Not confirmed. CVE-2026-17940 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-17940?
CVE-2026-17940 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-17940?
Yes. A fix has been recorded for CVE-2026-17940. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17940 affect?
CVE-2026-17940 affects Google Chrome for Android <151.0.7922.72, Chromium-based Android browsers (unpatched). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17940?
Update Chrome for Android to 151.0.7922.72 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape leading to potential arbitrary code execution on Android Chrome via crafted HTML when renderer process is compromised.
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.