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

CVE-2026-14390 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-14390?

Google Chrome remote code execution vulnerability (CVE-2026-14390, CVSS 9.6) affects all desktop users running versions prior to 150.0.7871.46; no public exploit identified at time of analysis.. A patch is available.

How to fix or mitigate CVE-2026-14390?

24 hours: Communicate critical vulnerability to all Chrome users; inventory systems running versions prior to 150.0.7871.46 as non-compliant. 7 days: Deploy Chrome 150.0.7871.46 or later across all managed desktop systems via auto-update and managed deployment channels (Windows, macOS, and Linux). 30 days: Complete endpoint audit to verify no vulnerable Chrome versions remain in active use; document remediation completion.

Google Chrome CVE-2026-14390

EUVD-2026-41197 CRITICAL

Use After Free (CWE-416)

2026-07-01 Chrome

GHSA-pg56-9pgf-wm9x

Denial Of Service Google Use After Free Memory Corruption 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

Network-reachable via a web page (AV:N) with no auth (PR:N) but requiring the victim to open it (UI:R); the sandbox escape crosses a trust boundary (S:C) with total impact.

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:28 vuln.today

CVSS changed

Jul 02, 2026 - 00:22 NVD

9.6 (CRITICAL)

CVE Published

Jul 01, 2026 - 22:22 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 01, 2026 - 22:22 cve.org

CRITICAL 9.6

DescriptionCVE.org

Use after free in ANGLE 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: High)

AnalysisAI

Sandbox escape in Google Chrome's ANGLE graphics layer lets a remote attacker who lures a victim to a crafted HTML page break out of the renderer sandbox and gain code execution in a higher-privilege context. All Chrome desktop builds prior to 150.0.7871.46 are affected. Chromium rated the underlying use-after-free High severity; no public exploit has been identified at time of analysis and SSVC records exploitation status as none.

Technical ContextAI

ANGLE (Almost Native Graphics Layer Engine) is Chromium's abstraction that translates WebGL/OpenGL ES calls into the platform's native graphics API (Direct3D on Windows, Metal on macOS, Vulkan/GL on Linux). It runs adjacent to the GPU process and is reachable from web content, making it a recurring browser attack surface. The flaw is CWE-416 (use-after-free): a graphics object is freed while a dangling reference remains, and subsequent use of that stale pointer corrupts memory. Because ANGLE straddles the boundary between the sandboxed renderer and the GPU process, a controllable UAF here can be leveraged to escape the sandbox rather than merely crashing the tab. CPE data confirms the affected component is cpe:2.3:a:google:chrome (all versions below the fixed build).

RemediationAI

Vendor-released patch: 150.0.7871.46 - update Google Chrome to 150.0.7871.46 or later on all desktop platforms (verify via chrome://settings/help, which triggers the update and requires a browser restart to take effect). Enterprises using managed rollouts should push the pinned version through their update/relaunch enforcement policy to close the window between release and user relaunch. Details are in the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. If patching must be deferred, the practical compensating controls are: keep the browser sandbox enabled (do not run Chrome with --no-sandbox); disable hardware-accelerated graphics via chrome://settings or the HardwareAccelerationModeEnabled policy to reduce reachability of ANGLE - the trade-off is degraded rendering/video performance and higher CPU use; and restrict browsing to trusted sites or enforce Enhanced Safe Browsing, since exploitation requires the user to load a crafted page. Chromium-based browsers should be updated once they rebase onto the fixed Chromium build.