What is the CVSS score of CVE-2026-14420?

CVE-2026-14420 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Google Chrome are affected by CVE-2026-14420?

Google Chrome versions prior to 150.0.7871.46 contain a critical sandbox escape vulnerability in the WebGPU implementation that allows arbitrary code execution on employee workstations through a…. A patch is available.

How to fix or mitigate CVE-2026-14420?

Within 24 hours: Audit deployed Chrome versions across the organization and identify systems running versions earlier than 150.0.7871.46. Within 7 days: Deploy Chrome 150.0.7871.46 or later to all affected systems via your standard patch management process; prioritize endpoints in high-risk roles (finance, engineering, executives). Within 30 days: Verify 100% patch compliance through automated inventory scans and monitor security logs for exploitation attempts targeting WebGPU functionality.

Google Chrome CVE-2026-14420

EUVD-2026-41175 CRITICAL

Out-of-bounds Read (CWE-125)

2026-07-01 Chrome

GHSA-g9cr-jqjw-cv33

Buffer Overflow Information Disclosure Google Red Hat Suse

9.6

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

9.6 CRITICAL

AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

vuln.today AI

9.6 CRITICAL

Remote crafted page needs no auth (PR:N) but requires the user to visit it (UI:R); the sandbox escape crosses a trust boundary (S:C) with total memory-corruption impact (C/I/A:H).

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

SUSE

CRITICAL

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 02, 2026 - 01:22 vuln.today

CVSS changed

Jul 02, 2026 - 00:22 NVD

9.6 (CRITICAL)

CVE Published

Jul 01, 2026 - 22:21 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 01, 2026 - 22:21 cve.org

CRITICAL 9.6

DescriptionCVE.org

Out of bounds read and write in Dawn in Google Chrome prior to 150.0.7871.46 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

AnalysisAI

Sandbox escape in Google Chrome's Dawn WebGPU implementation prior to 150.0.7871.46 lets a remote attacker use a crafted HTML page to trigger an out-of-bounds read and write, potentially breaking out of the renderer sandbox. Rated Critical by Chromium with a CVSS of 9.6 (scope-changed), it requires the victim to visit a malicious page but no authentication. There is no public exploit identified at time of analysis and it is not listed in CISA KEV.

Technical ContextAI

Dawn is Chromium's open-source implementation of the WebGPU standard, translating web-facing GPU API calls into native graphics backends (Vulkan, Metal, D3D12). Because WebGPU exposes low-level buffer and command handling to untrusted JavaScript, memory-safety bugs here are especially dangerous. The root cause is CWE-125 (Out-of-bounds Read), reported alongside an out-of-bounds write, indicating a bounds-checking failure in Dawn's handling of GPU resources or command buffers. An OOB read/write within the GPU process is a classic primitive for corrupting adjacent memory and escaping the renderer sandbox, consistent with the CVSS scope change (S:C). The affected component is the browser binary itself (cpe:2.3:a:google:chrome).

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.46 or later via the Stable channel (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); relaunch the browser to complete the update since Chrome does not apply the fix until restart. In managed environments, push the update through enterprise auto-update policies and verify the running version. As an interim compensating control before patching, WebGPU can be disabled to remove the vulnerable attack surface - set the chrome://flags/#enable-unsafe-webgpu flag off or block WebGPU via enterprise policy - at the cost of breaking GPU-accelerated web applications that rely on WebGPU. Downstream Chromium-based browsers should be updated to a build incorporating the fixed Dawn code.