# CVE-2026-14417: Google Chrome use after free in Dawn

Source: https://junglewise.ai/threats/cve-2026-14417-google-chrome-use-after-free-in-dawn  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-07-01. Updated: 2026-07-01  
License: CC BY 4.0 with a link back

CVE-2026-14417 · Severity: info · CVSS 10 · Published 2026-07-01

A critical security vulnerability has been identified in Google Chrome's Dawn component, which handles high-performance graphics. An attacker could exploit this flaw by tricking a user into visiting a specially crafted website, potentially allowing them to bypass the browser's security sandbox. If successful, this could lead to unauthorized access to the underlying operating system and sensitive user data.

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

## Quick answers

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

**How severe is CVE-2026-14417?** Informational severity, with a CVSS score of 10, published 1 July 2026.

**Which products and versions are affected?** Google Chrome Prior to 150.0.7871.46.

**Is there a fix for CVE-2026-14417?** A patch was published on 2026-06-30: Fixed in Chrome 150.0.7871.46/.47 stable channel update. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

**Am I affected by CVE-2026-14417?** 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 Dawn, the WebGPU implementation in Google Chrome. The flaw is triggered when the browser incorrectly manages memory during the processing of graphics-related tasks. A remote, unauthenticated attacker can exploit this by inducing a user to load a malicious HTML page, leading to arbitrary code execution outside of the browser's sandbox environment. This vulnerability is tracked as CVE-2026-14417 and was addressed in Chrome version 150.0.7871.46.

## Affected products

- Google Chrome Prior to 150.0.7871.46

## Timeline

- 2026-06-30: patched: Fixed in Chrome 150.0.7871.46/.47 stable channel update.
- 2026-07-01: advisory: NVD published the CVE record.

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html)
- [https://issues.chromium.org/issues/516649133](https://issues.chromium.org/issues/516649133)

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