EUVD-2026-66086
GHSA-cpwj-484x-44xf
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
AC:H reflects the mandatory renderer-compromise prerequisite; C:H retained because cross-origin cookie theft yields high confidentiality impact if chain completes.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
3DescriptionCVE.org
Improper input validation in Cookies 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: Low)
AnalysisAI
Cookie input validation bypass in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to circumvent web origin policy restrictions. Exploitation requires a second-stage attack where a separately compromised renderer is leveraged via a crafted HTML page, making this a chained exploit component rather than a standalone initial-access vulnerability. …
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 distinct preconditions: first, the attacker must have already achieved code execution within a Chrome renderer process through a separate, independent vulnerability - this is a non-trivial prerequisite that substantially limits the exploitable population. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 6.5 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) overstates standalone exploitability because the NVD vector does not encode the critical prerequisite: the attacker must have already compromised the renderer process, which typically requires a separate, independent exploit. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has separately exploited a memory-corruption or logic bug in Chrome's renderer process (for example, via a malicious or attacker-controlled web page) uses this cookie validation flaw as a second stage: the compromised renderer submits a crafted HTML page containing malformed cookie data to exfiltrate session cookies or authentication tokens belonging to a different origin, bypassing SOP. No public proof-of-concept code for this specific CVE has been identified at time of analysis, making opportunistic exploitation unlikely without the renderer-compromise prerequisite. |
| Remediation | The primary fix is upgrading Google Chrome to version 152.0.7977.65 or later, which is confirmed available via 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 weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today