EUVD-2026-65841
GHSA-p3h5-95vp-qqr9
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects mandatory prior renderer compromise and race condition timing requirements; C:L and I:N/A:N match the limited cross-origin read-only impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Race condition in Workers in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Web Workers race condition in Google Chrome prior to 152.0.7977.65 enables Same-Origin Policy bypass for attackers who have already achieved renderer process compromise. The flaw (CWE-367 TOCTOU) allows a timing attack between origin validation and Worker data access, permitting cross-origin data reads from within a compromised renderer. …
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 | Prior compromise of the Chrome renderer process is an explicit prerequisite stated in the CVE description - this vulnerability functions as a second-stage exploit and cannot be leveraged independently without a separate renderer RCE or equivalent primitive. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 3.1 score of 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) understates practical attack complexity: the description explicitly requires prior renderer compromise, a substantial multi-exploit prerequisite not reflected in AC:L. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate Chrome renderer process vulnerability to gain arbitrary code execution within the sandboxed renderer. From that position, they load a crafted HTML page that spawns a malicious Worker and triggers the TOCTOU race between origin validation and cross-origin data access, reading sensitive content (e.g., authentication tokens or financial data) from another origin the victim has open in the same browser session. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later via Chrome's built-in auto-update mechanism or the vendor stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today