EUVD-2026-65835
GHSA-mx2v-6pg3-9p82
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-compromise precondition; UI:R retained for social engineering; C:L only as origin policy bypass yields limited cross-origin read.
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 Core in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Incorrect authorization in Google Chrome Core prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to bypass the web origin policy by combining that foothold with social engineering via a crafted HTML page. The flaw is classified CWE-863 (Incorrect Authorization), meaning the browser's Core incorrectly validates authorization checks across origins under this specific post-compromise condition. …
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: first, the attacker must have already compromised the Chrome renderer process through a separate, independent vulnerability - this is a mandatory precondition, not an optional path. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-assigned CVSS of 4.3 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) warrants scrutiny: the AC:L and PR:N metrics are inconsistent with the description, which explicitly requires a prior renderer compromise - a high-complexity precondition that AC:L does not reflect. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already exploited a separate Chrome renderer vulnerability to achieve renderer process compromise then delivers a crafted HTML page to the victim and uses social engineering to obtain required user interaction. The malicious page triggers the incorrect authorization check in Chrome's Core, allowing the attacker to bypass the web origin policy and read limited cross-origin data that would otherwise be inaccessible to the compromised renderer. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later via the stable channel; this is the vendor-released patch confirmed by both the Chrome Releases advisory and EUVD-2026-65835. … 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