EUVD-2026-40649
GHSA-hqg2-xpfr-4wgv
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Matches vendor-provided vector: network delivery, high complexity due to required UI gesture sequencing, no auth needed, user interaction required, confidentiality-only impact with no integrity or availability effect.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in DevTools in Google Chrome on Windows prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Process memory disclosure in Google Chrome DevTools on Windows (versions prior to 150.0.7871.47) allows a remote attacker to read potentially sensitive data from browser process memory by serving a crafted HTML page and convincing a user to perform specific UI gestures. The flaw stems from insufficient input validation (CWE-20) within the DevTools subsystem and is limited to the Windows platform. …
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 three concurrent conditions: (1) the victim must be running Google Chrome on Windows (macOS/Linux are not affected); (2) the victim must visit an attacker-controlled or attacker-influenced HTML page; and (3) the victim must perform 'specific UI gestures' as described in the NVD entry - passive page loading alone is insufficient, meaning the attacker must also socially engineer the user into deliberate interaction, likely involving DevTools activation or manipulation. … 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 (Medium), reflecting a meaningful tension between signals: the Confidentiality impact is rated High (process memory access can expose tokens, credentials, or PII), but exploitation is substantially gated by AC:H (high complexity) and UI:R (required user interaction). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page designed to manipulate Chrome DevTools input processing on Windows, then lures a victim (e.g., via phishing or a malicious link) to visit the page and perform specific UI gestures - most likely opening DevTools or interacting with a DevTools panel while the crafted content is loaded. Upon triggering the insufficient validation flaw, the attacker's page receives fragments of browser process memory, potentially containing session tokens, credentials, or cached sensitive data. … |
| Remediation | The primary fix is to update Google Chrome on Windows to version 150.0.7871.47 or later, available through Chrome's built-in update mechanism (Settings → Help → About Google Chrome) or via enterprise deployment tools. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allSame 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