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

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

Google Chrome versions prior to 150.0.7871.47 contain a sandbox escape vulnerability in the ANGLE graphics component that could allow an attacker with renderer-level code execution to escalate…. A patch is available.

How to fix or mitigate CVE-2026-13834?

Within 24 hours, audit all Chrome deployments to identify current versions and usage patterns, prioritizing systems with access to sensitive web applications. Within 7 days, deploy Chrome version 150.0.7871.47 or later across all endpoints using your standard update mechanism (Microsoft Intune, Google Update, or equivalent). Within 30 days, verify completion of the patch deployment through audit logs and configure automated Chrome updates if not already enabled to prevent similar delays on future releases.

Google Chrome CVE-2026-13834

EUVD-2026-40520 HIGH

Improper Input Validation (CWE-20)

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

GHSA-6j9r-8w6g-vxcw

Information Disclosure Google Red Hat

8.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) 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

Requires a crafted page (UI:R) plus prior renderer compromise and winning the ANGLE bug (AC:H); sandbox escape crosses the trust boundary (S:C) with full GPU-process 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:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

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 22, 2026 - 20:00 vuln.today

CVE Published

Jun 30, 2026 - 23:16 cve.org

HIGH 8.3

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Insufficient validation of untrusted input in ANGLE 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: High)

AnalysisAI

Sandbox escape in Google Chrome's ANGLE graphics component (versions prior to 150.0.7871.47) lets an attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, escalating from renderer-level code execution to the more privileged GPU/browser context. Google rates the Chromium severity as High and a vendor patch is available; there is no public exploit identified and it is not listed in CISA KEV, with EPSS exploitation probability low at 0.21%.

Technical ContextAI

ANGLE (Almost Native Graphics Layer Engine) is Chrome's translation layer that maps WebGL/OpenGL ES calls onto the host platform's native graphics APIs (Direct3D, Metal, Vulkan, desktop GL). It runs in the GPU process and consumes untrusted, renderer-supplied command streams, making it a recurring sandbox-escape surface. The root cause is CWE-20 (Improper Input Validation): ANGLE insufficiently validates untrusted input reaching it from a compromised renderer, so maliciously crafted graphics commands can drive memory corruption or unexpected state that crosses the renderer/GPU trust boundary. CPE data scopes this to cpe:2.3:a:google:chrome (all versions before the fix); the same code also ships in other Chromium-based browsers, which typically inherit the ANGLE fix downstream.

RemediationAI

Vendor-released patch: Chrome 150.0.7871.47 - update to this version or later on the Stable channel via the Chrome release announcement at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html, then relaunch the browser to apply the update. In managed fleets, push the update through enterprise policy and force a restart to close the window. If immediate patching is not possible, reduce the surface that feeds ANGLE by disabling hardware-accelerated graphics/WebGL (chrome://settings 'Use graphics acceleration when available' off, or the WebGL/3D-APIs enterprise policies), accepting the trade-off of degraded rendering performance and broken WebGL-dependent sites, and enforce strict Site Isolation to raise the cost of the prerequisite renderer compromise. Users of other Chromium-based browsers should apply their vendor's corresponding update once released.