EUVD-2026-65907
GHSA-w3v6-7h77-mx3h
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
AV:N for web delivery, AC:H for required prior renderer compromise, UI:R for victim page load, C:H for sensitive network-layer data exposure, I:N and A:N as only confidentiality is affected.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Information leak in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Network-layer information disclosure in Google Chrome prior to 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to exfiltrate sensitive network-layer data by delivering a crafted HTML page to a victim. The CVSS score of 5.3 reflects constrained real-world risk: high confidentiality impact is offset by the requirement for a prior renderer compromise and active user interaction. …
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 chained preconditions explicitly stated in the CVE description and corroborated by the CVSS vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N yields a base score of 5.3, which accurately reflects the chained nature of this vulnerability: AC:H is driven by the requirement that the attacker must first compromise the renderer process through a separate exploit before this information leak becomes reachable. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a malicious HTML page that first exploits a separate renderer vulnerability to gain control of the Chrome renderer process, then leverages this network information leak to read sensitive network-layer state - such as cached authentication tokens or request metadata - accessible to the compromised renderer. The attacker delivers this page to a target via phishing or a compromised web property, and once the victim loads the page, the chained exploit silently exfiltrates the sensitive data to an attacker-controlled endpoint. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, which is confirmed as the fixed release per the stable channel 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-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today