# CVE-2026-9892: Google Chrome Skia sandbox escape on Android

Source: https://junglewise.ai/threats/cve-2026-9892-google-chrome-skia-sandbox-escape-on-android  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-28. Updated: 2026-05-28  
License: CC BY 4.0 with a link back

CVE-2026-9892 · Severity: info · CVSS 9.8 · Published 2026-05-28

A critical security vulnerability has been identified in Google Chrome for Android's graphics engine, Skia. This flaw could allow a malicious website to break out of the browser's security sandbox, which is the primary layer of defense that keeps web content isolated from the rest of the device. If exploited, an attacker could gain unauthorized access to the underlying Android operating system, potentially leading to the theft of sensitive data or full device compromise.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-9892 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-9892 being exploited in the wild.

**How severe is CVE-2026-9892?** Informational severity, with a CVSS score of 9.8, published 28 May 2026.

**Which products and versions are affected?** Google Chrome prior to 148.0.7778.216.

**Is there a fix for CVE-2026-9892?** A patch was published on 2026-05-27: Fixed in Chrome for Android version 148.0.7778.216 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-9892 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-9892?** Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A sandbox escape vulnerability exists in the Skia graphics component of Google Chrome for Android. The flaw is categorized as an 'inappropriate implementation' that can be triggered via a specially crafted HTML page. An attacker who has already achieved code execution within the sandboxed renderer process can leverage this vulnerability to bypass the sandbox boundary and execute arbitrary code with the privileges of the browser process or the underlying operating system. This is a multi-stage attack requiring an initial renderer compromise. Google has addressed this in version 148.0.7778.216.

## Affected products

- Google Chrome for Android prior to 148.0.7778.216

## Timeline

- 2026-05-27: patched: Fixed in Chrome for Android version 148.0.7778.216
- 2026-05-28: disclosed: CVE published by NVD

## References

- [https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html](https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html)
- [https://issues.chromium.org/issues/513948178](https://issues.chromium.org/issues/513948178)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)