Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome for Android (widely deployed browser) enabling code execution outside sandbox; high-impact, broadly used product warranting org-wide attention.

Mobile

CVE-2026-102331

9.6
Critical
EPSS n/aPatch availableSep 30, 2026

Critical RCE in Chrome for Android via crafted HTML (ANGLE).

common questions

Is CVE-2026-102331 being exploited?

Not confirmed. CVE-2026-102331 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.

How severe is CVE-2026-102331?

CVE-2026-102331 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-102331?

Yes. A fix has been recorded for CVE-2026-102331. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-102331 affect?

CVE-2026-102331 affects Google Chrome for Android < 154.0.8037.92, Android devices running vulnerable Chrome builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-102331?

Update Chrome for Android to 154.0.8037.92 or later immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome for Android < 154.0.8037.92Android devices running vulnerable Chrome builds
impact

Remote code execution outside Chrome sandbox via crafted HTML, allowing arbitrary code execution on affected Android devices.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 154.0.8037.92

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free