EUVD-2026-65817
GHSA-6j37-mh6c-p74w
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Renderer-compromise prerequisite elevates AC to H; same-origin policy bypass crosses security boundaries warranting S:C; integrity impact added for potential cross-origin write capability.
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
Incorrect authorization in Extensions 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
Incorrect authorization in the Chrome Extensions subsystem (CWE-863) allows a remote attacker who has already compromised the renderer process to bypass the web origin policy by delivering a crafted HTML page, affecting all Chrome desktop versions prior to 152.0.7977.65. Chromium rated this High severity despite the NVD CVSS base score of 4.3, because the same-origin policy bypass has meaningful privacy implications even though it requires a pre-compromised renderer as a prerequisite. …
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 - either via a separate, concurrently exploited renderer vulnerability or through another pre-existing compromise mechanism. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N = 4.3) materially understates the attack complexity: the description explicitly requires a pre-compromised Chrome renderer process, which contradicts AC:L and PR:N. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-process vulnerability in a victim's Chrome browser (via a malicious or compromised website), gaining code execution within the sandboxed renderer. From that position, they serve a crafted HTML page that invokes the flawed Extensions authorization path, bypassing the same-origin policy and reading sensitive cross-origin resources - such as authenticated session data or page content from a banking or intranet origin open in another tab. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later; this is the vendor-confirmed fixed release per the Chrome stable-channel update advisory at 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-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today