Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Delivered via web page (AV:N, UI:R) but gated on a prior renderer compromise and defeating sandbox policy (AC:H); sandbox escape crosses trust boundary (S:C) with total impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in Chrome for iOS in Google Chrome on iOS prior to 150.0.7871.47 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 for iOS prior to 150.0.7871.47 lets a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, escalating from renderer-level code execution to broader access on the device. The flaw stems from insufficient policy enforcement (CWE-20) and carries a High Chromium severity rating with a CVSS 8.3 (scope-changed) score. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process - this CVE is the sandbox-escape stage, not the initial foothold, so a prior renderer-level code-execution primitive is a hard prerequisite. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and point to a real-but-conditional risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A victim using an unpatched Chrome for iOS visits an attacker-controlled page that first exploits a separate renderer bug to gain code execution inside the sandboxed renderer, then chains this insufficient-policy-enforcement flaw via crafted HTML to escape the sandbox and reach higher-privileged context. No public exploit code has been identified, and the high attack complexity plus required renderer compromise make this a targeted, multi-stage operation rather than opportunistic mass exploitation. |
| Remediation | Vendor-released patch: 150.0.7871.47 - update Google Chrome for iOS to 150.0.7871.47 or later via the Apple App Store, which is the primary and complete fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Notify all iOS users and device administrators to update Chrome to version 150.0.7871.47 or later. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40499
GHSA-mccm-g2cw-25j9