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

CVE-2026-15769 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.3%.

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

Google Chrome on Linux versions prior to 150.0.7871.125 contain a sandbox escape vulnerability (CVE-2026-15769) that could allow system compromise from a compromised browser process.. A patch is available.

How to fix or mitigate CVE-2026-15769?

Within 24 hours, inventory all Linux systems running Google Chrome and identify instances prior to version 150.0.7871.125; prioritize systems that are internet-facing or process sensitive data. Within 7 days, update all affected systems to Chrome version 150.0.7871.125 or later, beginning with pilot environments and high-risk systems, and validate successful patching through your endpoint management platform. Within 30 days, complete organization-wide deployment of the patch, enforce automatic Chrome update policies to maintain version 150 or later, and verify full closure through endpoint monitoring.

Google Chrome CVE-2026-15769

EUVD-2026-44476 HIGH

Improper Input Validation (CWE-20)

2026-07-14 Chrome

GHSA-f3vq-gjqx-3pg9

Information Disclosure Google 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 AC:H for the difficult escape and PR:N/UI:R per Chrome's renderer-attacker convention, with S:C and C/I/A:H reflecting full host impact after sandbox escape.

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:04 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

Insufficient validation of untrusted input in Linux Toolkit Theming in Google Chrome on Linux 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 on Linux prior to 150.0.7871.125 allows an attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page, chaining from renderer compromise to broader host access. The flaw resides in the Linux Toolkit Theming component (CWE-20, insufficient input validation) and is rated High by Chromium with a CVSS of 8.3. There is no public exploit identified at time of analysis, EPSS is low (0.26%), and CISA SSVC lists exploitation status as none, so this is a defense-in-depth-critical but not currently exploited issue.

Technical ContextAI

The vulnerability lives in Chrome's Linux Toolkit Theming code path, the browser-process logic that renders native GTK/desktop-toolkit widget styling on Linux. Because theming is handled outside the renderer sandbox, data flowing from a compromised renderer into this component crosses a trust boundary; CWE-20 (Improper Input Validation) means the theming code fails to adequately validate that untrusted input before acting on it, giving a compromised renderer a path to influence higher-privileged browser-process execution. The affected component is platform-specific: only Chrome (and Chromium-derived) builds on Linux are exposed, per CPE cpe:2.3:a:google:chrome and the description scoping to 'on Linux'. The CVSS scope-change flag (S:C) reflects exactly this sandbox-to-host boundary crossing.

RemediationAI

Vendor-released patch: update Google Chrome on Linux to 150.0.7871.125 or later via the Stable channel (advisory: https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0353146366.html); ChromeOS users should apply the corresponding ChromeOS stable update (http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-chromeos_01375142362.html). Confirm the running version via chrome://version and relaunch to complete the update, since Chrome stages updates but only applies them on restart. As a compensating control until patched, restrict browsing to trusted sites and enable enterprise auto-update / forced-relaunch policies to shrink the exposure window; because the exploit requires a prior renderer compromise, keeping Chrome's site isolation and sandbox enabled (do not launch with --no-sandbox) materially reduces the chance an attacker reaches this component. Chromium-derived Linux browsers should pull the equivalent upstream fix.