Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Extensions 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: Medium)
AnalysisAI
Information disclosure in Google Chrome's Extensions subsystem prior to version 149.0.7827.53 enables a remote attacker who has already compromised the renderer process to read potentially sensitive data from process memory by delivering a crafted HTML page. This is a second-stage vulnerability requiring a pre-existing renderer compromise as a hard prerequisite, making it a chained attack component rather than a standalone exploit. No public exploit code exists and CISA has not added this to the KEV catalog; the EPSS score of 0.03% and SSVC exploitation-status of 'none' are mutually consistent with no observed active exploitation.
Technical ContextAI
Google Chrome uses a multi-process sandboxed architecture in which renderer processes are isolated from the main browser process and from cross-origin data. The Extensions subsystem mediates privileged communication between web content and installed extensions, and a flaw classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) exists in how this subsystem is implemented. An 'inappropriate implementation' in this context typically means the Extensions component fails to enforce memory access boundaries correctly when handling inputs from a compromised renderer, allowing out-of-bounds or cross-boundary reads of process memory contents. Affected versions span all Google Chrome releases below 149.0.7827.53 across all desktop platforms, as confirmed by EUVD entry EUVD-2026-34629. No explicit CPE string was provided in the source data, but the fix boundary at 149.0.7827.53 is confirmed by the vendor advisory.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later immediately; this is the vendor-released patch confirmed by the Google Chrome Releases stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's automatic update mechanism will handle this for consumer endpoints; enterprise administrators should verify rollout completion via Chrome Browser Cloud Management or applicable group policy and confirm the installed version is at or above 149.0.7827.53. As a compensating control in environments where immediate patching is delayed, restricting extension installation to an approved allowlist via enterprise policy reduces the attack surface of the Extensions subsystem involved in this flaw - note that this may impact productivity for users relying on unapproved extensions. Because exploitation requires a prior renderer compromise, ensuring other browser security features such as site isolation and sandbox enforcement are not disabled is an additional defensive measure with no functional trade-off.
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34629
GHSA-6682-gq2x-qwh3