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

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

A sandbox escape vulnerability in Google Chrome and ChromeOS versions prior to 150.0.7871.125 allows attackers to break out of browser isolation following renderer compromise, enabling full system…. A patch is available.

How to fix or mitigate CVE-2026-15774?

Within 24 hours: inventory all Chrome and ChromeOS systems in use and identify instances below version 150.0.7871.125. Within 7 days: deploy Chrome 150.0.7871.125 or later to all affected systems, prioritizing endpoints handling sensitive data or accessing critical applications. Within 30 days: validate 100% deployment completion across the enterprise and enable Chrome auto-update policies to prevent version drift.

Google Chrome CVE-2026-15774

EUVD-2026-44481 HIGH

Use After Free (CWE-416)

2026-07-14 Chrome

GHSA-fvwf-cx56-8x5c

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

Kept PR:N/UI:R/S:C per Chrome sandbox-escape convention with AC:H for the hard-to-win UAF; total impact (C/I/A:H) reflects browser-process code execution, though a prior renderer compromise is realistically required.

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

9.0 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:01 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 Skia in Google Chrome 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 desktop and ChromeOS builds prior to 150.0.7871.125 stems from a use-after-free in the Skia graphics library, allowing a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. Google rates this High severity; SSVC technical impact is 'total' with a scope change (S:C), but exploitation is not observed (no public exploit identified at time of analysis) and EPSS is low at 0.24%. A vendor patch is available.

Technical ContextAI

The flaw lives in Skia, Chromium's open-source 2D graphics rendering engine used for drawing web content, canvas, and UI compositing. CWE-416 (Use After Free) means a memory object in Skia is freed but a dangling reference is later dereferenced, letting an attacker corrupt heap memory and hijack control flow. Because Skia runs in a privileged context relative to the renderer, corrupting it from an already-exploited renderer enables the scope change to the higher-privileged browser process. The affected CPE is cpe:2.3:a:google:chrome across all editions, with the parallel ChromeOS stable channel also patched.

RemediationAI

Vendor-released patch: 150.0.7871.125 - update Google Chrome to 150.0.7871.125 or later on all desktop platforms and apply the corresponding ChromeOS stable channel update, then fully restart the browser so the new binary loads. Chrome auto-updates for most users, but enterprises using managed or pinned versions should force the rollout and verify via chrome://settings/help. No standalone workaround exists for the Skia bug itself, but because exploitation requires first compromising the renderer, enabling and enforcing the site isolation and sandbox hardening that ship by default meaningfully raises the bar; avoid running Chrome with sandbox-disabling flags (e.g. --no-sandbox), which would remove the very boundary this bug targets. Refer to the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.html) for the authoritative fixed-version list.