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.