Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Network in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
Use-after-free in the Network component of Google Chrome prior to version 149.0.7827.53 enables an attacker who has already compromised the renderer process to read potentially sensitive data from process memory by delivering a crafted HTML page. The Changed scope (S:C) in the CVSS vector confirms the vulnerability crosses security boundaries - specifically from the renderer sandbox into the Network process - making this a secondary exploitation step rather than an initial access vector. No public exploit code exists and the vulnerability is not listed in the CISA KEV catalog; Google has released a patched stable channel build.
Technical ContextAI
CWE-416 (Use After Free) describes a memory-management flaw where a program continues to reference a memory region after it has been freed. In Chrome's multi-process architecture, the Network service process handles socket and protocol operations separately from the renderer. A use-after-free in the Network component can corrupt internal state in a way that allows a controlled read of freed memory contents, leaking data that was previously resident in that region. The CVSS Changed Scope (S:C) attribute reflects Chrome's process isolation model: the vulnerability bridges the renderer sandbox boundary into the Network service, which is a distinct privilege domain. The attack is delivered via a crafted HTML page (AV:N, UI:R), consistent with web-based renderer exploitation patterns. Affected versions are all Chrome releases prior to 149.0.7827.53 per EUVD-2026-34710.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later immediately - this is the vendor-released patch per the Stable Channel update advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's auto-update mechanism should apply this update automatically on most managed and consumer deployments; administrators should verify version compliance via fleet management tooling. Because exploitation requires prior renderer compromise, organizations that have not yet deployed the patch should prioritize isolating high-value endpoints and monitoring for renderer exploitation indicators (e.g., unexpected child process spawning from Chrome's renderer) as a compensating control. Disabling JavaScript would prevent renderer-based exploitation paths but would break broad web functionality and is not a practical long-term workaround for most environments. No additional workarounds are documented in the available references.
Same weakness CWE-416 – Use After Free
View allSame technique Denial Of Service
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34710
GHSA-356f-525v-w9xh