EUVD-2026-65807
GHSA-rq7c-38w9-8xh5
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Race condition inherently requires timing precision (AC:H); prior renderer compromise treated as PR:L; impact limited to cross-origin data disclosure (C:L only).
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 Autofill 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: High)
AnalysisAI
Race condition in Google Chrome's Autofill subsystem (versions prior to 152.0.7977.65) enables a remote attacker who has already compromised the renderer process to bypass the browser's same-origin policy via a crafted HTML page. This is a second-stage vulnerability requiring a prior renderer exploit, making it a chained-attack component rather than a standalone threat. …
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 simultaneous conditions: (1) the target user must visit a crafted HTML page, satisfying the user-interaction prerequisite reflected in the CVSS UI:R metric; and (2) the attacker must have already compromised the Chrome renderer process - a significant technical prerequisite that makes this a second-stage chained vulnerability, not a standalone remote exploit. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS base score of 4.3 (Medium) appropriately reflects constrained real-world impact: the attack requires user interaction (UI:R) and, critically, a pre-existing compromised renderer process, which is a non-trivial prerequisite indicating this flaw operates as a second-stage link in an exploit chain. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-level vulnerability in Chrome to gain code execution within the sandboxed renderer process, then serves a crafted HTML page that triggers timing-sensitive Autofill interactions designed to win the race condition. By winning the race, the compromised renderer bypasses same-origin policy and reads data - such as form field contents or session-related data - from other web origins without user awareness. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later via Chrome's built-in auto-update mechanism or through the 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 weakness CWE-362 – Race Condition
View allSame technique Race Condition
View allShare
External POC / Exploit Code
Leaving vuln.today