# CVE-2026-8511: Google Chrome use after free in UI

Source: https://junglewise.ai/threats/cve-2026-8511-google-chrome-use-after-free-in-ui  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-14. Updated: 2026-05-18  
License: CC BY 4.0 with a link back

CVE-2026-8511 · Severity: critical · CVSS 9.6 · Published 2026-05-14

A critical security vulnerability exists in the Google Chrome web browser's user interface component. By tricking a user into visiting a specially crafted website, an attacker could bypass the browser's security sandbox. This could allow the attacker to gain unauthorized access to the underlying operating system, potentially leading to data theft or the installation of malicious software.

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

## Quick answers

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

**How severe is CVE-2026-8511?** Critical severity, with a CVSS score of 9.6, published 14 May 2026.

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

**Is there a fix for CVE-2026-8511?** A patch was published on 2026-05-12: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-8511 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-8511?** 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 use-after-free (UAF) vulnerability exists in the User Interface (UI) component of Google Chrome. The flaw is triggered when the browser incorrectly manages memory for UI objects, allowing an attacker to reference memory after it has been freed. By leveraging a crafted HTML page, a remote, unauthenticated attacker can exploit this memory corruption to achieve a sandbox escape. This allows code execution outside of the restricted browser process at the privilege level of the user. The vulnerability is addressed in Chrome version 148.0.7778.168.

## Affected products

- Google Chrome prior to 148.0.7778.168

## Timeline

- 2026-03-22: disclosed: Reported by Google internally
- 2026-05-12: patched: Stable channel update released
- 2026-05-14: advisory: NVD publication date

## References

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

## 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)