EUVD-2026-65782
GHSA-9jhr-52w2-jgh9
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Network delivery via crafted page, AC:H for race timing plus renderer pre-compromise; scope change to OS justifies S:C and full C/I/A impact.
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
Race condition in FileSystem in Google Chrome prior to 152.0.7977.65 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: High)
AnalysisAI
Sandbox escape via race condition in Google Chrome's FileSystem component (prior to 152.0.7977.65) allows a remote attacker who has already compromised the renderer process to execute arbitrary code outside the sandbox through a crafted HTML page. This is a scope-changing exploit chain primitive - it operates as a second-stage attack requiring renderer access first, not a standalone unauthenticated RCE. …
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 | Two conditions must both be satisfied: (1) the attacker must have already achieved renderer process compromise - a significant prerequisite typically requiring a separate, chained browser vulnerability such as a V8 engine or IPC flaw; (2) the victim must actively visit or be redirected to a crafted HTML page that exercises the vulnerable FileSystem code path (UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 High score is driven by AV:N (web-delivered), S:C (full sandbox escape), and a C:H/I:H/A:H impact triad, but AC:H and UI:R meaningfully constrain realistic exploitability. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker targeting a specific user first delivers a separate browser exploit (e.g., a V8 JavaScript engine vulnerability) via a malicious or compromised website to achieve renderer process compromise. From that foothold, the attacker serves a crafted HTML page that repeatedly triggers Chrome's FileSystem component, racing the TOCTOU window until the race is won and a manipulated file handle passes sandbox validation. … |
| Remediation | The primary fix is upgrading Google Chrome to version 152.0.7977.65 or later, which contains the vendor-released patch addressing this TOCTOU race condition. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, verify the current Chrome versions deployed across your organization and confirm patch availability in your update mechanisms. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today