Chrome is ubiquitous; an Android browser sandbox escape can let attackers break isolation and access device data across enterprises.
CVE-2026-17681
Chrome Android sandbox escape via crafted WebAuthn page (pre-151.0.7922.72)
Is CVE-2026-17681 being exploited?
Not confirmed. CVE-2026-17681 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.56% probability of exploitation in the next 30 days.
How severe is CVE-2026-17681?
CVE-2026-17681 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-17681?
Yes. A fix has been recorded for CVE-2026-17681. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17681 affect?
CVE-2026-17681 affects Google Chrome for Android < 151.0.7922.72. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17681?
Update Chrome for Android to 151.0.7922.72+ immediately and restrict untrusted web content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape allowing attacker (after compromising renderer) to execute code outside browser sandbox and access device data.
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.