EUVD-2026-65977
GHSA-r66f-j54q-cm44
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects the mandatory renderer-compromise prerequisite; C:L captures limited cross-origin data leak; no integrity or availability impact applies to this information-disclosure-only flaw.
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 BFCache in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Cross-origin data exfiltration via the BFCache mechanism in Google Chrome prior to 152.0.7977.65 enables an attacker who has already compromised the renderer process to read data across origin boundaries using a crafted HTML page. This information disclosure (CWE-200) is a second-stage capability, not a standalone attack - it requires chaining with a separate renderer RCE vulnerability, constraining real-world risk significantly. …
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 inside the Chrome renderer process via a separate, unrelated vulnerability - this is an explicit precondition stated in the CVE description, not an inference. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-assigned CVSS score is 3.1 (Low) with vector AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N, reflecting high attack complexity and limited confidentiality impact - both of which are well-grounded. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate Chrome renderer RCE vulnerability to gain code execution inside the sandboxed renderer process, then serves a crafted HTML page that manipulates BFCache behavior to access and exfiltrate cross-origin cached page content - such as session tokens or sensitive page data from a previously visited site. No public exploit code exists at the time of analysis; this scenario requires chaining two vulnerabilities and active user interaction. |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, released via the stable channel and documented 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