Affects widely-used Chrome on Android; sandbox escape could compromise devices across industries.
CVE-2026-11131
Chrome for Android Autofill use-after-free enables sandbox escape.
Is CVE-2026-11131 being exploited?
Not confirmed. CVE-2026-11131 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-11131?
CVE-2026-11131 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-11131?
Yes. A fix has been recorded for CVE-2026-11131. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11131 affect?
CVE-2026-11131 affects Google Chrome for Android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11131?
Update to latest Chrome for Android (>=149.0.7827.53)
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape from a compromised renderer via crafted HTML, enabling potential code execution and sandbox breakout.
Immediate action required
- affected< 149.0.7827.53
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.