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

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

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

Google Chrome desktop versions prior to 150.0.7871.47 contain a critical vulnerability (CVE-2026-13775, CVSS 9.8) enabling complete system compromise if the browser is targeted in an attack chain.. A patch is available.

How to fix or mitigate CVE-2026-13775?

Within 24 hours: Identify all endpoints running Chrome versions prior to 150.0.7871.47 and classify by risk. Within 7 days: Deploy Chrome version 150.0.7871.47 or later organization-wide via automated update mechanisms. Within 30 days: Verify complete adoption of the patched version and confirm no systems remain on affected versions.

Google Chrome CVE-2026-13775

EUVD-2026-40461 CRITICAL

Use After Free (CWE-416)

2026-06-30 chrome-cve-admin@google.com

GHSA-3hc5-9533-fp2f

Denial Of Service Google Use After Free Memory Corruption Red Hat Suse

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

vuln.today AI

8.0 HIGH

AC:H and PR:L reflect the required pre-existing renderer compromise, UI:R for loading the crafted page, S:C for the renderer-to-GPU sandbox escape, and high C/I/A from GPU-process code execution.

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

4.0 AV:N/AC:H/AT:P/PR:L/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 NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 16:00 vuln.today

CVSS changed

Jul 01, 2026 - 15:52 NVD

9.8 (CRITICAL)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 nvd

CRITICAL 9.8

DescriptionNVD

Use after free in GPU in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

AnalysisAI

Sandbox escape in Google Chrome desktop prior to 150.0.7871.47 stems from a use-after-free in the GPU process, letting a remote attacker who has already compromised the renderer break out of the browser sandbox via a crafted HTML page. Google rates the Chromium severity as Critical, and a fix is available in the Stable channel update. There is no public exploit identified at time of analysis, and EPSS exploitation probability is low at 0.22% (13th percentile).

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's GPU process, the privileged component that handles GPU-accelerated rendering, compositing, and WebGL/WebGPU commands on behalf of sandboxed renderer processes over Chromium's Mojo IPC interfaces. In Chromium's multi-process security model, renderer processes are heavily sandboxed while the GPU process runs at higher privilege; a dangling pointer to freed memory in the GPU process can be reclaimed and manipulated to corrupt memory in that more-privileged context, enabling code execution outside the renderer sandbox. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* identifies Google Chrome (all desktop builds before the fixed version) as the affected product; the underlying Chromium engine means Chromium-derived browsers may share the defect, though only Google Chrome is enumerated here.

RemediationAI

Vendor-released patch: 150.0.7871.47 - upgrade Google Chrome desktop to 150.0.7871.47 or later via the Stable channel and restart the browser to apply, per the advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Chrome auto-updates for most users, so confirm the running version under chrome://settings/help and force a relaunch across managed fleets. As an interim compensating control before patching, you can reduce GPU-process attack surface by launching Chrome with GPU acceleration disabled (the --disable-gpu flag or the 'Use graphics acceleration when available' setting turned off), which forces software rendering and can blunt GPU-process exploitation - with the trade-off of degraded rendering performance and broken WebGL/WebGPU/hardware-video features. Since exploitation first requires a compromised renderer, keeping Chrome and its renderer-side components fully patched and enabling Enhanced Safe Browsing further limits the initial foothold needed to reach this bug.