EUVD-2026-74411
GHSA-rj97-j5w8-2fqx
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H reflects required renderer pre-compromise; S:C captures sandbox escape to host; UI:R for victim page visit; full C/I/A post-escape.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Improper input validation in FileAPI in Google Chrome prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
FileAPI improper input validation in Google Chrome prior to 153.0.8010.36 enables an attacker who has already compromised the renderer process to escape Chrome's sandbox and execute arbitrary code on the underlying host system. The flaw, tracked in Chromium issue 532957878, was addressed in the September 2026 stable channel release. …
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 two chained prerequisites: (1) the attacker must have already achieved code execution within the Chrome renderer process via a separate, independently exploitable vulnerability, and (2) the victim user must load attacker-controlled HTML content in the affected Chrome version (UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) captures the chained nature of this flaw: AC:H reflects the prerequisite renderer-process compromise, and S:C reflects the sandbox escape to the host OS. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | The primary fix is to update Google Chrome to version 153.0.8010.36 or later, confirmed as the patched release in the Chrome stable channel advisory (https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory Chrome deployments and document current version numbers across all systems. …
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 allShare
External POC / Exploit Code
Leaving vuln.today