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

CVE-2026-17749 has a contested CVSS base score of 9.6 from a third party (e.g. CISA-ADP), while the vendor rates it Critical. vuln.today uses the vendor rating as authoritative.

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

Google Chrome versions prior to 151.0.7922.72 contain a critical sandbox escape vulnerability enabling code execution with user privileges.. A patch is available.

How to fix or mitigate CVE-2026-17749?

Within 24 hours, audit Chrome desktop deployments and enable automatic updates across your fleet. Within 7 days, deploy Chrome 151.0.7922.72 or later to all endpoints, prioritizing users who handle sensitive data, and issue guidance on extension installation risks. Within 30 days, verify patch compliance, implement extension allowlisting policies to restrict installation to approved applications, and monitor browser logs for suspicious extension activity.

Google Chrome CVE-2026-17749

EUVD-2026-50699 CRITICAL

Improper Input Validation (CWE-20)

2026-07-30 Chrome

GHSA-m2g4-4j4w-r7q3

Information Disclosure Google

Critical

Disputed · 9.6 Vendor: Chrome

Severity by source

Sources disagree (Medium–Critical)

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

9.6 CRITICAL

Delivery is network-borne but the attack hinges on the user installing a malicious extension (UI:R); no app privilege is needed (PR:N), and the sandbox escape changes scope (S:C) with full C/I/A loss.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

SUSE

CRITICAL

qualitative

Red Hat

8.6 MEDIUM

qualitative

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

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

Aug 03, 2026 - 19:40 vuln.today

CVSS changed

Aug 03, 2026 - 17:37 NVD

9.6 (None) 9.6 (CRITICAL)

Patch available

Jul 30, 2026 - 02:02 EUVD

CVE Published

Jul 30, 2026 - 00:19 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 30, 2026 - 00:19 cve.org

CRITICAL 9.6

DescriptionCVE.org

Insufficient validation of untrusted input in Extensions in Google Chrome prior to 151.0.7922.72 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (Chromium security severity: Medium)

AnalysisAI

Sandbox escape in Google Chrome desktop prior to 151.0.7922.72 allows an attacker who tricks a user into installing a malicious extension to break out of the renderer/extension sandbox via a crafted extension exploiting insufficient input validation. The flaw was reported internally by the Chrome team and carries an NVD CVSS of 9.6, though Chromium rates the security severity only Medium and SSVC shows no known exploitation; no public exploit identified at time of analysis. A vendor patch is available, and exploitation hinges on the significant precondition of the victim installing an attacker-controlled extension.

Technical ContextAI

The vulnerability lives in Chrome's Extensions subsystem, which runs extension logic (background service workers, content scripts, and extension pages) inside a security sandbox intended to isolate untrusted extension code from the browser broker process and the host OS. The root cause is CWE-20 (Improper Input Validation): the extension IPC/API surface fails to sufficiently validate untrusted input supplied by a crafted extension, letting that input drive privileged code paths outside the sandbox boundary. A sandbox escape here means malicious extension-controlled code can influence the higher-privileged browser process, which is why NVD marks Scope as Changed (S:C). The single affected product per CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* across all desktop channels below the fixed build.

RemediationAI

Vendor-released patch: update Google Chrome to 151.0.7922.72 or later per the Chrome Stable channel advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); confirm the update landed via chrome://settings/help and relaunch, since the fix only takes effect after restart. Because the attack requires a malicious extension, the highest-value compensating control is extension governance: enforce an enterprise ExtensionInstallAllowlist / ExtensionInstallBlocklist (set the blocklist to '*' and allowlist only vetted IDs) and disable installation of extensions from outside the Chrome Web Store, which prevents sideloaded or attacker-supplied CRX files at the cost of blocking unvetted productivity extensions users may want. Restricting extension installation to admins and enabling Chrome auto-update / keeping the browser current further reduces exposure; these controls have minimal side effects beyond added extension-approval overhead. Prioritize normal patch cadence given the low EPSS and no observed exploitation.