EUVD-2026-66006
GHSA-7g9h-jqqc-h39m
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Renderer compromise prerequisite and required user interaction justify AC:H and UI:R; read-only cross-origin leak caps impact at C:L with no integrity or availability consequence.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Information leak in CORS in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data exposure in Google Chrome before 152.0.7977.65 enables a chained information leak when a renderer process has already been compromised by a separate exploit. Chrome's CORS implementation incorrectly permits cross-origin data access from within a compromised renderer, allowing a remote attacker to exfiltrate data from origins the victim is authenticated to via a crafted HTML page. …
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 prerequisites: first, the attacker must have already achieved compromise of the Chrome renderer process through a separate, independent vulnerability - this is stated directly in the CVE description and confirmed by the AC:H CVSS metric; without renderer compromise, this CORS flaw cannot be triggered. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 3.1 (Low) with vector AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N accurately reflects a constrained risk profile. … 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 vulnerability in a victim's Chrome session delivers a crafted HTML page - via a malicious advertisement, a compromised third-party site, or a phishing link - that leverages the CORS flaw to read sensitive data from a cross-origin resource the victim is authenticated to, such as a session-bound REST API response or an authenticated web application's user data. The extracted data could then be exfiltrated to an attacker-controlled server. … |
| Remediation | Upgrade Google Chrome to version 152.0.7977.65 or later, available via Chrome's built-in auto-update mechanism or directly referenced in the vendor 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-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today