Skip to main content

Google Chrome EUVDEUVD-2026-50917

| CVE-2026-17991 CRITICAL
Improper Input Validation (CWE-20)
2026-07-30 Chrome GHSA-c4r5-cggq-5cfm
Critical
Disputed · 9.6 Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Compromise Chrome renderer process
  2. Delivery
    Lure victim to crafted HTML page
  3. Exploit
    Feed malformed input to AI component
  4. Execution
    Trigger insufficient input validation
  5. Persist
    Escape sandbox to browser process
  6. Impact
    Gain higher-privilege code context

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process - this is a sandbox-escape second stage, not an initial-access vector - and additionally requires the victim to load a crafted HTML page (UI:R). The specific vulnerable surface is the AI component reachable from the renderer, triggered via malformed untrusted input. Limiting factors: the mandatory pre-existing renderer compromise (typically needing a chained memory-corruption exploit), required user interaction of visiting a malicious page, and the desktop-stable Chrome build being older than 151.0.7922.72. These preconditions are why Google rates the Chromium severity 'Low' despite the 9.6 CVSS.

Impact

Signals conflict sharply and must be weighed together. The NVD CVSS of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C, full C/I/A impact) looks critical, but the description explicitly requires 'a remote attacker who had compromised the renderer process' - a substantial precondition that AC:L understates; a sandbox escape is a second-stage exploit, not a standalone entry point. Google's own Chromium severity is 'Low', EPSS is 0.17% (7th percentile), and CISA SSVC records Exploitation: none and Automatable: no, though Technical Impact is total. Taken together this is a defense-in-depth boundary bug: dangerous only when chained to a prior renderer RCE, not a widely exploitable network-facing critical. The CVSS-vs-Chromium-severity gap should be read as scoring methodology difference, not evidence of imminent mass exploitation - patch it on the normal Chrome update cadence rather than as an emergency.

Exploit ScenarioDerived

An attacker first compromises the Chrome renderer through a separate memory-corruption bug, then lures the victim to a crafted HTML page that feeds malformed input to the AI component, using that as a pivot to escape the sandbox into the higher-privileged browser process. No public exploit is identified at time of analysis, and the multi-stage requirement (renderer foothold plus user visiting the page) makes opportunistic exploitation unlikely.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 30, 2026

Sandbox escape in Google Chrome desktop before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out to higher-privileged browser context via a crafted HTML page, rooted in insufficient validation of untrusted input in the AI component (CWE-20). NVD rates it CVSS 9.6 while Google labels the Chromium security severity 'Low', reflecting that renderer compromise is a hard prerequisite; there is no public exploit identified at time of analysis and EPSS is low at 0.17%. A vendor patch is available and CISA SSVC records exploitation as none.

RemediationAI

Vendor-released patch: 151.0.7922.72 - upgrade Chrome to 151.0.7922.72 or later via the Stable Channel desktop update and restart the browser to apply it, as described at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome auto-updates by default, so confirm the update actually installed (chrome://settings/help) across managed fleets rather than assuming it applied. Until patched, reduce exposure by ensuring users restart browsers promptly and, where the affected AI feature is governed by enterprise policy, disabling it removes the vulnerable code path at the cost of losing that functionality; because exploitation also requires a separate renderer compromise, keeping site isolation enabled and avoiding untrusted browsing meaningfully limits the practical attack surface.

Affected VersionsENISA

Chrome 151.0.7922.72 <151.0.7922.72

Affected Packages

euvd chrome fix: 151.0.7922.72

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw sits in Chrome's AI subsystem and is classified CWE-20 (Improper Input Validation), meaning data crossing a trust boundary is consumed without adequate checks. In Chromium's multi-process architecture the renderer runs untrusted web content inside a sandbox, and the privileged browser process is meant to be isolated from it; a sandbox escape defeats that boundary. The affected code path processes untrusted input reaching the AI feature from an already-hostile renderer, allowing that content to influence higher-privilege logic. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* identifies all Chrome builds prior to 151.0.7922.72 on the desktop stable channel.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Sources disagree (Low–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 8.3 HIGH

AC:H because exploitation requires first chaining a separate renderer compromise; UI:R since the victim must load a crafted page; S:C and full C/I/A reflect the sandbox escape to the browser process.

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
Red Hat 4.3 LOW

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

3
Patch available
Jul 30, 2026 - 02:02 EUVD
CVE Published
Jul 30, 2026 - 00:25 cve.org
UNKNOWN (no severity yet)
CVE Published
Jul 30, 2026 - 00:25 cve.org
CRITICAL 9.6

DescriptionCVE.org

Insufficient validation of untrusted input in AI in Google Chrome 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: Low)

Executive ViewAI

Why It Matters

Google Chrome desktop (before version 151.0.7922.72) contains a critical sandbox escape vulnerability in its AI component that could enable system-level compromise if an attacker has previously compromised the browser renderer process. Although no public exploit is identified at time of analysis, the CRITICAL severity designation and widespread Chrome deployment across organizations necessitates rapid patching to mitigate exploitation risk.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
Ubiquitous
Chrome is the most widely deployed desktop web browser globally
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
SUSE Package Hub 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy