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

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

Google Chrome for Android versions prior to 150.0.7871.125 contain a high-severity sandbox escape (CVE-2026-15772, CVSS 8.3) that allows attackers who have already compromised the browser renderer to…. A patch is available.

How to fix or mitigate CVE-2026-15772?

Within 24 hours, audit Android device inventories through mobile device management (MDM) solutions to identify installed Chrome versions below 150.0.7871.125. Within 7 days, deploy Chrome for Android version 150.0.7871.125 or later across all managed and unmanaged mobile devices. Within 30 days, verify patch deployment completion through MDM reporting and confirm all Android devices have updated to the patched version or later.

Google Chrome CVE-2026-15772

EUVD-2026-44479 HIGH

Use After Free (CWE-416)

2026-07-14 Chrome

GHSA-ph5f-pjvp-h9x6

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

Delivered via crafted HTML over the network (AV:N, UI:R) with difficult memory-grooming and a renderer-compromise prerequisite (AC:H); sandbox escape crosses a trust boundary (S:C) with total impact on the GPU process (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

CRITICAL

qualitative

Red Hat

8.3 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 22, 2026 - 13:03 vuln.today

Patch available

Jul 14, 2026 - 23:20 EUVD

CVSS changed

Jul 14, 2026 - 21:22 NVD

8.3 (HIGH)

CVE Published

Jul 14, 2026 - 20:09 cve.org

HIGH 8.3

DescriptionCVE.org

Use after free in GPU in Google Chrome on Android prior to 150.0.7871.125 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 for Android (versions prior to 150.0.7871.125) stems from a use-after-free in the GPU process, allowing an attacker who has already compromised the renderer to break out of the browser sandbox via a crafted HTML page. Rated High by Chromium with a CVSS of 8.3, it carries a scope-changing, total-impact profile but is gated by prior renderer compromise, and there is no public exploit identified at time of analysis. EPSS is low (0.24%, 16th percentile) and CISA SSVC records exploitation status as none.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's GPU process, the component that handles accelerated graphics, WebGL, and GPU-accelerated compositing on behalf of untrusted renderer content. In Chromium's multi-process architecture the GPU process is more privileged than the sandboxed renderer, so a dangling-pointer condition reachable through the renderer-to-GPU IPC boundary can be groomed to corrupt memory in that higher-privileged process. The affected component (cpe:2.3:a:google:chrome) is the Android build; a use-after-free occurs when GPU-side objects are freed while still referenced, letting an attacker reclaim and control the freed allocation to redirect execution or corrupt state - the classic root cause behind browser sandbox escapes.

RemediationAI

Vendor-released patch: update Google Chrome on Android to 150.0.7871.125 or later; the fix is delivered through the Stable channel update announced on Google's Chrome Releases blog (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.html and the ChromeOS post http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-chromeos_01375142362.html). Ensure Play Store auto-updates are enabled so mobile fleets receive the build, and fully restart the browser to load it. As an interim compensating control before patching, disable GPU hardware acceleration (chrome://settings, 'Use graphics acceleration when available') to reduce reachability of the vulnerable GPU-process paths, accepting the trade-off of degraded rendering and video performance; because exploitation also requires a compromised renderer first, keeping the browser and Site Isolation fully current is the most effective additional mitigation.