EUVD-2026-40768
GHSA-727w-cq94-9wj2
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network delivery via extension install, no attacker privileges needed, but active user interaction (UI:R) is mandatory; only confidentiality is impacted via memory read.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in DevTools in Google Chrome prior to 150.0.7871.47 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
Insufficient policy enforcement in Chrome's DevTools component allows a crafted malicious extension to read potentially sensitive data from process memory. Affected versions are all Google Chrome releases prior to 150.0.7871.47 on desktop platforms. …
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 the victim to actively install a malicious Chrome Extension authored by the attacker - this is confirmed by the description ('convinced a user to install a malicious extension') and the CVSS UI:R metric. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 6.5 score is driven primarily by the C:H (High confidentiality) impact reflecting that process memory can hold highly sensitive artifacts such as authentication tokens, passwords autofilled by the browser, or decrypted page content. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker builds a Chrome extension that appears legitimate - for example, a productivity tool or ad-blocker - and hosts it on a third-party site or sends a targeted phishing link to install it outside the Chrome Web Store. Once the victim installs and runs the extension, it invokes DevTools APIs through the insufficiently enforced policy boundary to scan the Chrome process memory, extracting session cookies, OAuth tokens, or page content from authenticated sessions the user currently has open. … |
| Remediation | Update Google Chrome to version 150.0.7871.47 or later, which contains the vendor-released patch per the Google Chrome Stable Channel advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today