Skip to content
major vulnerability· requires attention

Remote code execution in a widely used browser (Chrome on Android) that can escape sandbox — impacts many organizations and mobile fleets.

Mobile

CVE-2026-85050

9.6
Critical
EPSS 0.33%Patch availableSep 4, 2026

Chrome for Android WebGL out-of-bounds write enables remote code execution.

common questions

Is CVE-2026-85050 being exploited?

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

How severe is CVE-2026-85050?

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

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

What does CVE-2026-85050 affect?

CVE-2026-85050 affects Google Chrome (Android) < 152.0.7977.82, WebGL component in Chrome for Android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85050?

Update Chrome on Android to 152.0.7977.82 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 (Android) < 152.0.7977.82WebGL component in Chrome for Android
impact

Remote code execution outside Chrome sandbox via crafted HTML/WebGL content on Android devices.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 152.0.7977.82

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