# CVE-2026-8580: Google Chrome use after free in Mojo

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

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

A vulnerability in Google Chrome's Mojo component could allow a malicious website to break out of the browser's security sandbox. This could allow an attacker to gain unauthorized access to the underlying operating system and user data. Users are protected by updating to the latest version of the Chrome browser.

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

## Quick answers

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

**How severe is CVE-2026-8580?** 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, Prior to 148.0.7778.168.

**Is there a fix for CVE-2026-8580?** A patch was published on 2026-05-12: Chrome Stable Channel Update released version 148.0.7778.167/168 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-8580?** 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 Mojo IPC framework within Google Chrome. The flaw is triggered when the browser improperly handles object lifecycles during communication between different browser processes. By enticing a user to visit a specially crafted HTML page, a remote attacker can exploit this memory corruption to execute arbitrary code and escape the Chrome sandbox. This vulnerability was addressed in Chrome version 148.0.7778.168 for Windows, Mac, and Linux.

## Affected products

- Google Chrome prior to 148.0.7778.168

## Timeline

- 2026-05-12: patched: Chrome Stable Channel Update released version 148.0.7778.167/168
- 2026-05-14: disclosed: CVE-2026-8580 published

## 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/496639647](https://issues.chromium.org/issues/496639647)

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