EUVD-2026-41164
GHSA-3x3p-qx4r-hmgh
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Remotely reachable via web content but AC:H and UI:R reflect the required renderer compromise and page visit; S:C and C/I/A:H capture the full sandbox escape.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in ANGLE in Google Chrome on Android prior to 150.0.7871.46 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's ANGLE graphics component on Android (versions prior to 150.0.7871.46) allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. Rated High by Chromium and CVSS 8.3, the flaw stems from improper validation of untrusted input in ANGLE and requires renderer compromise plus user interaction as prerequisites. …
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 Chrome's renderer process (a separate renderer RCE primitive is a hard prerequisite) and that the victim opens a crafted HTML page (UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are moderately consistent but point to a bounded rather than urgent threat. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer-process exploit (e.g., a V8 or Blink bug) to gain code execution inside Chrome's sandboxed renderer when a victim on Android visits a malicious page. From that foothold, the attacker feeds crafted graphics input through ANGLE that triggers the input-validation flaw, escaping the sandbox to reach more privileged browser/GPU process context. … |
| Remediation | Update Google Chrome to version 150.0.7871.46 or later (Vendor-released patch: 150.0.7871.46), which is distributed automatically through the Chrome stable channel and the Google Play Store on Android; verify via chrome://settings/help and restart the browser to apply. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Verify current Chrome versions deployed across Android fleet. …
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