Affects widely used Chrome for Android; DAC bypass could affect many devices/users.
CVE-2026-13852
Local DAC bypass in Chrome for Android via crafted HTML page
Is CVE-2026-13852 being exploited?
Not confirmed. CVE-2026-13852 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-13852?
CVE-2026-13852 is rated Critical with a CVSS score of 9.1. 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-13852?
Yes. A fix has been recorded for CVE-2026-13852. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13852 affect?
CVE-2026-13852 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-13852?
Update Chrome for Android to latest version immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can bypass discretionary access control via crafted HTML, accessing restricted data in Chrome for Android
Immediate action required
- affected< 150.0.7871.47
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.