EUVD-2026-65989
GHSA-7g44-h2mq-8527
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Renderer compromise prerequisite warrants AC:H; delivery requires no attacker credentials (PR:N); impact is confidentiality-only with no integrity or availability effect.
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 before 152.0.7977.65 enables a remote attacker who has already compromised the renderer process to exfiltrate sensitive data by directing a victim to a crafted HTML page. The attack is a multi-stage chain: the renderer compromise is a hard prerequisite not satisfied by this CVE alone, which materially constrains real-world exploitability. …
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 has two hard prerequisites: (1) the attacker must have already compromised the Chrome renderer process through a separate vulnerability - CVE-2026-79220 is not a standalone exploit and cannot be used to achieve initial renderer access; (2) the victim must interact with a crafted HTML page (UI:R), requiring some delivery mechanism such as phishing, malvertising, or a watering-hole attack. … 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 scores 5.3, and the component signals are internally consistent: high confidentiality impact is offset by high attack complexity driven by the mandatory renderer-compromise prerequisite, which itself requires a separate, distinct vulnerability to be exploited first. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate Chrome renderer vulnerability (e.g., a memory corruption flaw) to gain code execution in the renderer process, then serves the victim a crafted HTML page that triggers the network information leak. The sensitive data exfiltrated - such as session tokens from authenticated network requests or responses from internal resources - can then be leveraged for lateral movement or session hijacking. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later, which is confirmed as the vendor-released patch per the 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-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today