EUVD-2026-50810
GHSA-pwgg-jhvp-wr6h
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted page
-
DeliveryCompromise renderer via prior exploit
-
ExploitSend malformed input across sandbox boundary
-
ExecutionTrigger CWE-20 validation flaw
-
PersistEscape renderer sandbox (scope change)
-
ImpactExecute in privileged browser 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 - the sandbox escape is a second stage, not a standalone entry point. The trigger is a crafted HTML page processed by the vulnerable validation logic, and the victim must load attacker-controlled content (UI:R / user interaction). Limiting factors: only Chrome for iOS builds before 151.0.7922.72 are affected; the attacker needs a functioning renderer exploit to reach the vulnerable code, meaning this cannot be leveraged without a prior bug or foothold; and it is bounded to Chrome's own process model on iOS. These prerequisites substantially narrow realistic exploitation despite the network attack vector. |
| Impact | Signals are mixed and should be weighed together rather than reading the 9.6 in isolation. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) drives the critical score largely through Scope:Changed and full C/I/A impact, but the description states a hard precondition - the attacker must have ALREADY compromised the renderer process - which the base vector does not capture as a required privilege. This is a second-stage/chain vulnerability, not a single-shot remote takeover. Corroborating this, EPSS is only 0.29% (21st percentile), there is no CISA KEV listing, and no POC is referenced, so real-world exploitation pressure is currently low. SSVC-style reading: exploitation = none observed, technical impact = total (sandbox escape), automatable = unlikely as a standalone step because it requires a working renderer exploit first. Net: a genuinely serious bug worth prompt patching on mobile fleets, but the CVSS-9.6 overstates standalone risk versus the chained, no-known-exploit reality. Note the conflict explicitly: CVSS shows PR:N while the description implies a prerequisite compromise - verify chaining assumptions with the vendor. |
| Exploit ScenarioDerived | A victim on an unpatched Chrome for iOS visits a page hosting a malicious script that first exploits a separate renderer bug to gain code execution inside the sandbox, then serves crafted HTML/input that triggers CVE-2026-17684 to escape the sandbox into the more privileged browser context. No public exploit is identified at time of analysis, and the attack depends on chaining with a working renderer exploit, so this remains a plausible but currently theoretical scenario. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Sandbox escape in Google Chrome for iOS before 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, escalating a contained renderer foothold into broader control (CVSS 9.6, scope-changed). Reported internally by the Chrome team under CWE-20 insufficient input validation; no public exploit identified at time of analysis, and EPSS is low at 0.29% (21st percentile), consistent with a chained bug that is not yet weaponized. Vendor-released patch is available in stable channel 151.0.7922.72.
RemediationAI
Vendor-released patch: update Google Chrome for iOS to 151.0.7922.72 or later via the Apple App Store; this is the primary and complete fix, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). In managed environments, push the update through MDM app-management policies and enable automatic App Store updates to shorten exposure. Because exploitation requires a prior renderer compromise, interim risk reduction focuses on preventing that first stage: keep the OS and any WebKit components current, avoid untrusted sites, and where policy allows restrict browsing to trusted destinations - with the trade-off that aggressive URL filtering degrades usability and does not address an already-compromised renderer. There is no feature-level toggle that disables the vulnerable code path without patching, so upgrading is the only reliable control.
Affected VersionsENISA
Affected Packages
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 affected component is Google Chrome's iOS build (cpe:2.3:a:google:chrome), which runs the Blink/rendering engine inside a sandboxed renderer process isolated from the more privileged browser process and the underlying OS. CWE-20 (Improper Input Validation) here means a boundary that accepts data from the untrusted renderer fails to sufficiently validate it, so a renderer that is already under attacker control can send malformed input that the higher-privilege side mishandles, enabling a sandbox escape. The CVSS Scope:Changed flag reflects exactly this trust-boundary crossing: the exploited component (renderer) and the impacted component (browser process/OS resources) are different security authorities. On iOS specifically, Chrome relies on Apple's WebKit/WKWebView constraints in addition to Chromium's own multiprocess sandbox, so the practical impact of an escape depends on the surrounding platform isolation.
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
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-delivered crafted page (AV:N/UI:R) escaping the renderer sandbox is a genuine trust-boundary crossing (S:C) with full C/I/A; PR kept N to match vendor convention despite the renderer-compromise prerequisite.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Insufficient validation of untrusted input in Chrome for iOS in Google Chrome on iOS 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
Executive ViewAI
Google Chrome for iOS contains a critical sandbox-escape vulnerability that could allow attackers to escalate a contained browser compromise into full device takeover, risking exposure of corporate data and system integrity. All iOS users using Chrome require immediate updates to prevent this two-stage attack chain.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Related Vulnerabilities in Google Chrome Prior to 151.0.7922.72 Security Flaws
View all 80Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB