# CVE-2026-126902: Google Chrome incorrect reference resolution in Browser sandbox escape

Source: https://junglewise.ai/threats/cve-2026-126902-incorrect-reference-resolution-in-browser-in-google-chrome-on-on  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-12  
License: CC BY 4.0 with a link back

CVE-2026-126902 · Severity: info · Published 2026-11-11

Google Chrome is a web browser used by billions of users to access websites and web applications. A vulnerability in the Browser component allows an attacker who has already compromised Chrome's renderer process to break out of the sandbox and execute arbitrary code with full browser privileges. This could lead to complete compromise of a user's system and sensitive data theft.

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

## Quick answers

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

**How severe is CVE-2026-126902?** Informational severity, published 11 November 2026.

**Which products and versions are affected?** Google Chrome prior to 157.0.8103.78 on macOS.

**Is there a fix for CVE-2026-126902?** Yes: fixed in Chrome 157.0.8103.78 and later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-126902?** 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.

## How to fix

- Fixed in Chrome 157.0.8103.78 and later

## Technical details

Incorrect reference resolution in the Browser component of Chrome on macOS prior to 157.0.8103.78 allows a remote attacker with a compromised renderer process to execute arbitrary code outside the sandbox. The vulnerability requires the renderer process to be already compromised, and is triggered via a crafted HTML page. A fix is available in Chrome 157.0.8103.78 and later.

## Affected products

- Google Chrome prior to 157.0.8103.78 on macOS

## Timeline

- 2026-11-11: disclosed

## References

- [https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html)
- [https://issues.chromium.org/issues/580867480](https://issues.chromium.org/issues/580867480)

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