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

CVE-2026-14412 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/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-14412?

Google Chrome versions prior to 150.0.7871.46 contain a vulnerability in the ANGLE graphics layer that enables attackers to escape the browser sandbox and gain complete system control if the browser…. A patch is available.

How to fix or mitigate CVE-2026-14412?

Within 24 hours: Identify all Chrome deployments and establish your update distribution process. Within 7 days: Deploy Chrome version 150.0.7871.46 or later organization-wide, prioritizing systems with administrative privileges. Within 30 days: Verify 100% deployment, review threat intelligence for related exploits, and document lessons learned for future critical patch response.

Google Chrome CVE-2026-14412

EUVD-2026-41167 HIGH

Improper Input Validation (CWE-20)

2026-07-01 Chrome

GHSA-gm8p-g47w-pwgf

Information Disclosure Google Red Hat Suse

8.3

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

8.3 HIGH

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

vuln.today AI

8.3 HIGH

Remote crafted page (AV:N, UI:R) but requires a pre-compromised renderer, so AC:H; sandbox escape crosses trust boundary (S:C) with total impact (C/I/A:H).

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

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

SUSE

HIGH

qualitative

Red Hat

8.2 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 02, 2026 - 01:24 vuln.today

CVSS changed

Jul 02, 2026 - 00:22 NVD

8.3 (HIGH)

CVE Published

Jul 01, 2026 - 22:21 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 01, 2026 - 22:21 cve.org

HIGH 8.3

DescriptionCVE.org

Insufficient validation of untrusted input in ANGLE in Google Chrome prior to 150.0.7871.46 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 150.0.7871.46) lets a remote attacker who has already compromised the renderer process break out of the browser sandbox by luring a victim to a crafted HTML page. This is a second-stage bug that chains with a prior renderer-level exploit rather than a standalone entry point; Chromium rates it High severity. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, with SSVC recording exploitation status as none.

Technical ContextAI

ANGLE (Almost Native Graphics Layer Engine) is Chrome's abstraction layer that translates OpenGL ES / WebGL calls onto native backends such as Direct3D, Metal, Vulkan, or desktop OpenGL. It runs across the renderer/GPU boundary and is a recurring source of sandbox-escape bugs because it processes attacker-influenceable graphics commands. The root cause is classified as CWE-20 (Improper Input Validation): insufficient validation of untrusted input passed into ANGLE allows memory-safety or logic conditions that can be leveraged to execute code outside the constrained renderer sandbox. Per the supplied CPE (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) the affected component is the Chrome desktop browser itself; because ANGLE is shared, other Chromium-based browsers (Edge, Brave, Opera) built on the same version line are likely affected pending their own advisories.

RemediationAI

Update Google Chrome to version 150.0.7871.46 or later on the Stable channel (Vendor-released patch: 150.0.7871.46 per the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html), then fully restart the browser so the new binary loads. In managed fleets, force the update via enterprise policy and confirm rollout, since Chrome's staged auto-update may otherwise delay coverage. If patching cannot be completed immediately, reducing exposure to hostile web content (enforcing Enhanced Safe Browsing, restricting untrusted browsing) lowers the odds of the prerequisite renderer compromise; note there is no clean feature-level toggle for ANGLE that preserves normal WebGL/graphics functionality, so disabling hardware acceleration is only a partial and disruptive mitigation that degrades rendering performance and does not fully eliminate the code path.