# CVE-2026-126901: Google Chrome use-after-free in PDF

Source: https://junglewise.ai/threats/cve-2026-126901-use-after-free-in-pdf-in-google-chrome-prior-to-157-0-8103-78  
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-126901 · Severity: info · Published 2026-11-11

Google Chrome is a web browser used by billions worldwide. A use-after-free bug in the PDF renderer allows attackers to execute arbitrary code within the browser sandbox by loading a specially crafted HTML page. While the sandbox limits direct system compromise, escaping it remains a critical risk.

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

## Quick answers

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

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

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

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

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

**Am I affected by CVE-2026-126901?** 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 (Windows, Mac, Linux)

## Technical details

A use-after-free vulnerability exists in Chrome's PDF component that an attacker can trigger via a crafted HTML page. The flaw allows remote code execution within the browser's sandbox; exploitation requires no user authentication but does require the user to visit a malicious page. A fix is available in version 157.0.8103.78 and later.

## Affected products

- Google Chrome prior to 157.0.8103.78

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

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