EUVD-2026-66055
GHSA-5m22-gjf7-v86f
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Prior renderer compromise is a hard prerequisite raising AC to H; origin policy bypass crosses security domains warranting S:C with limited cross-origin read (C:L) and full integrity bypass (I:H).
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
Incorrect authorization in StorageAccessAPI 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
StorageAccessAPI incorrect authorization in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to bypass web origin policy via a crafted HTML page, achieving high-integrity impact against cross-origin resources. The flaw (CWE-863) is a post-exploitation second-stage primitive: it cannot be leveraged without a preceding renderer compromise, substantially narrowing its realistic threat scope beyond what the CVSS 6.5 score implies. …
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 explicit conditions: first, the attacker must have already compromised the Chrome renderer process through a separate vulnerability - this is a stated prerequisite in the CVE description, not an inferred condition, and it is the primary limiting factor on real-world exploitability. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The NVD CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N overstates standalone exploitability by assigning AC:L and PR:N without accounting for the explicit prerequisite stated in the description: the attacker must have already compromised the Chrome renderer process before this flaw is reachable. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has separately achieved code execution in a Chrome renderer process - for example through an unpatched renderer memory corruption vulnerability - then directs the compromised renderer to load a crafted HTML page that invokes the StorageAccessAPI with a malformed or unauthorized request. Chrome's flawed authorization logic in the API grants access to cross-origin storage it should deny, allowing the attacker to read session storage, cookies, or other first-party data belonging to a different web origin loaded in the same browser. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, the vendor-released patch confirmed by the Chrome 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-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today