Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the mandatory renderer-process compromise prerequisite; C:L for limited cross-origin data exposure; no integrity or availability impact applies.
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
Operation on a resource after expiration or release in Network 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
Remote same-origin policy bypass in Google Chrome prior to 152.0.7977.65 exploits a use-after-free condition (CWE-672) in the Network component, allowing an attacker who has already achieved renderer process compromise to escape origin boundaries via a crafted HTML page. The vulnerability carries a CVSS 4.3 and EPSS of 0.66% (49th percentile), consistent with its role as a second-stage exploit chain component rather than a standalone initial-access vector. …
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 that the attacker has already achieved code execution within the Chrome renderer process via a separate, independent vulnerability - this prerequisite is explicitly stated in the CVE description ('a remote attacker who had compromised the renderer process'). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The reported CVSS 3.1 score of 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) encodes the outer attack surface but does not capture the mandatory prerequisite of prior renderer process compromise, which substantially raises effective attack complexity beyond what AC:L implies. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already exploited a separate renderer-process remote code execution vulnerability delivers a crafted HTML page to the victim's compromised Chrome renderer. The page triggers the use-after-free condition in Chrome's Network component, causing same-origin policy enforcement to malfunction and allowing the attacker's renderer code to read cross-origin HTTP responses - for example, authenticated API replies or session cookies from a co-loaded web application. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later; this is the vendor-confirmed patched build documented in the Chrome Stable Channel update 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
EUVD-2026-65843
GHSA-9j23-gv58-cfxh