EUVD-2026-34699
GHSA-4vvh-qc7h-f4ch
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in DevTools in Google Chrome prior to 149.0.7827.53 allowed an attacker who convinced a user to install a malicious extension to obtain potentially sensitive information from process memory via a crafted Chrome Extension. (Chromium security severity: Low)
AnalysisAI
Inappropriate implementation in Google Chrome's DevTools component prior to version 149.0.7827.53 allows a crafted Chrome Extension to access and read sensitive data from process memory. Exploitation requires social engineering a target user into installing a malicious extension, after which the extension can invoke under-guarded DevTools APIs to extract potentially sensitive in-memory content such as credentials, tokens, or session data. No public exploit has been identified at time of analysis, and the EPSS score of 0.01% indicates very low observed exploitation probability; however, the confidentiality impact is rated High by CVSS.
Technical ContextAI
Google Chrome's DevTools subsystem exposes debugging and inspection APIs intended for developer use. CWE-306 (Missing Authentication for Critical Function) identifies the root cause: DevTools functionality capable of reading process memory lacks adequate access controls or authorization checks, allowing a crafted Chrome Extension to invoke these APIs without meeting the authentication barrier appropriate for such sensitive operations. The affected CPE corresponds to Google Chrome desktop builds prior to 149.0.7827.53. The 'Authentication Bypass' tag in the intelligence data corroborates the CWE-306 classification - the extension bypasses the expected gating mechanism that should restrict process memory inspection to privileged or explicitly authorized contexts. The CVSS vector (AV:N/AC:H/PR:N/UI:N) indicates network-accessible attack surface with high complexity, though this conflicts with the description's requirement for user interaction to install the malicious extension - a discrepancy discussed further in risk assessment.
RemediationAI
The primary fix is to update Google Chrome to version 149.0.7827.53 or later, which contains the vendor-released patch for this vulnerability. The update is available via Chrome's built-in auto-update mechanism or manually through the Chrome releases blog at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. As a compensating control prior to patching, organizations should enforce Chrome extension allowlisting via enterprise policy (ExtensionInstallAllowlist / ExtensionInstallBlocklist) to prevent installation of unauthorized extensions - this directly addresses the prerequisite social engineering vector. Disabling developer mode in Chrome via policy (DeveloperToolsAvailability) can further restrict DevTools access in managed environments, though this may impact legitimate developer workflows. No workaround fully eliminates the underlying DevTools API exposure without the patch.
Same technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today