Skip to content
major vulnerability· requires attention

Ubiquitous Google Chrome on Android; RCE outside the sandbox with high CVSS can lead to widespread device compromise and merits org-wide attention.

Web

CVE-2026-87438

9.6
Critical
EPSS 0.55%Patch availableSep 9, 2026

Chrome for Android WebGL OOB write enables remote code execution (fixed in 153.0.8010.36).

common questions

Is CVE-2026-87438 being exploited?

Not confirmed. CVE-2026-87438 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.55% probability of exploitation in the next 30 days.

How severe is CVE-2026-87438?

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

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

What does CVE-2026-87438 affect?

CVE-2026-87438 affects Google Chrome for Android <153.0.8010.36. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-87438?

Update Chrome for Android to 153.0.8010.36 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 <153.0.8010.36
impact

Remote code execution outside Chrome sandbox via crafted HTML/WebGL, enabling full device compromise and arbitrary code execution on Android.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 153.0.8010.36

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