Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the hard prerequisite of prior renderer process compromise, substantially increasing real-world complexity beyond the official AC:L rating.
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
Missing authorization 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
Web origin policy bypass in Google Chrome's Network component (all versions prior to 152.0.7977.65) grants a remote attacker who has already compromised the renderer process the ability to circumvent Same-Origin Policy restrictions via a crafted HTML page, leaking limited confidential data from cross-origin contexts. This is a second-stage exploitation primitive - it is only dangerous when chained with a separate renderer compromise 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 has two hard prerequisites: first, the attacker must have already achieved arbitrary code execution within Chrome's renderer process via a separate, independent vulnerability - this is not a configuration option but a required prior exploitation step. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The official CVSS 3.1 score of 4.3 Medium (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) materially understates the prerequisite attack complexity: the AC:L metric does not capture the hard requirement that the renderer process must already be independently compromised. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has independently achieved code execution within a victim's Chrome renderer process - through a separate vulnerability such as a heap corruption or type confusion flaw - serves the victim a crafted HTML page that leverages the missing Network authorization check to issue cross-origin requests. The Network component fails to block these requests, allowing the attacker to read responses from origins where the victim holds an authenticated session, such as internal web applications. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later, the vendor-released patched version documented in the stable channel release 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-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65985
GHSA-874q-wq72-pqhp