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

CVE-2026-17692 has a CVSS 3.1 base score of 9.6 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/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-17692?

Google Chrome on Windows contains a critical vulnerability that undermines the browser's security isolation, potentially allowing attackers to gain system-level access through sophisticated…. A patch is available.

How to fix or mitigate CVE-2026-17692?

Within 24 hours, identify all Windows systems running Chrome and determine which handle sensitive workloads or administrative functions. Within 7 days, deploy Google Chrome 151.0.7922.72 or later across all Windows endpoints, prioritizing systems with elevated privileges or access to sensitive data. Within 30 days, verify complete patch deployment and establish monitoring for exploitation attempts or anomalous browser activity.

Google Chrome CVE-2026-17692

EUVD-2026-50818 CRITICAL

Use After Free (CWE-416)

2026-07-30 Chrome

GHSA-j42h-vr42-mvr8

Denial Of Service Google Use After Free Memory Corruption Microsoft

9.6

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

9.6 CRITICAL

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

vuln.today AI

8.0 HIGH

Requires a pre-compromised renderer (PR:L) and non-trivial UAF timing (AC:H) plus user interaction; sandbox escape crosses a trust boundary (S:C) with full host impact.

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:N/PR:L/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

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 30, 2026 - 16:38 vuln.today

Patch available

Jul 30, 2026 - 02:02 EUVD

CVE Published

Jul 30, 2026 - 00:18 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 30, 2026 - 00:18 cve.org

CRITICAL 9.6

DescriptionCVE.org

Use after free in DataTransfer in Google Chrome on Windows prior to 151.0.7922.72 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)

Articles & Coverage 1

News 12 New Chrome Vulnerabilities - 8 Critical, 4 High Severity Jul 30, 2026

AnalysisAI

Sandbox escape in Google Chrome on Windows before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process leverage a use-after-free in the DataTransfer component (clipboard/drag-and-drop data) to break out of the browser sandbox via a crafted HTML page. Rated High by Chromium with a CVSS 9.6 driven by scope change and full CIA impact, though EPSS is low (0.29%) and there is no public exploit identified at time of analysis. It is not on CISA KEV and requires an existing renderer compromise plus user interaction, making it a second-stage bug in an exploit chain rather than a standalone entry point.

Technical ContextAI

The flaw is a CWE-416 use-after-free in DataTransfer, the Blink/Chromium object that backs clipboard and drag-and-drop data exchanged between web content and the browser. A use-after-free occurs when memory is freed but a dangling reference is later dereferenced, allowing an attacker to control the reused allocation and corrupt program state. Because DataTransfer bridges the sandboxed renderer and higher-privileged browser process, corrupting it is a path to escaping the renderer sandbox. The affected CPE is cpe:2.3:a:google:chrome on Windows; Chromium tagged it High severity and it is tracked internally as chromium issue 517350808.

RemediationAI

Vendor-released patch: 151.0.7922.72 - update Google Chrome on Windows to 151.0.7922.72 or later, per the Chrome Stable Channel advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome auto-updates, but confirm the version via chrome://settings/help and relaunch to apply, and push the update through enterprise management (Google Update / group policy) to ensure fleet coverage. Since this bug requires a pre-compromised renderer as a chain link, defense-in-depth that reduces initial renderer compromise helps: enable site isolation (default on) and consider enabling the enhanced/strict Safe Browsing setting to reduce exposure to malicious pages, with the trade-off of some telemetry sent to Google and occasional false-positive warnings. There is no need to disable DataTransfer/clipboard functionality as a workaround; patching is straightforward and the primary control.