EUVD-2026-40656
GHSA-vw9m-cqmx-vwfc
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-delivered malicious file (AV:N) but requires victim DevTools gestures and non-trivial conditions (UI:R, AC:H); no privileges (PR:N); code execution yields high C/I/A but stays within the renderer sandbox (S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in DevTools in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who convinced a user to engage in specific UI gestures to execute arbitrary code inside a sandbox via a malicious file. (Chromium security severity: Medium)
AnalysisAI
Arbitrary code execution in Google Chrome's DevTools component (versions prior to 150.0.7871.47) lets a remote attacker run code inside the renderer sandbox after luring a victim into performing specific UI gestures with a malicious file. Rated Medium by Chromium but scored CVSS 7.5, the flaw stems from insufficient validation of untrusted input (CWE-20); no public exploit identified at time of analysis and EPSS exploitation probability is low at 0.24% (15th percentile).
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 attacker to deliver a malicious file AND convince the victim to perform specific UI gestures within Chrome DevTools to load/process that file (UI:R) - this user-interaction requirement and the high attack complexity (AC:H) are the primary limiting factors. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and point to elevated-but-not-critical priority. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts or emails a crafted malicious file and uses social engineering to get a developer or power user to load it into Chrome DevTools and perform particular interface actions (e.g., dragging, importing, or opening the file within a DevTools panel). The malformed input bypasses validation and executes attacker-controlled code inside the browser's renderer sandbox. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later via the Stable Channel Update for Desktop advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); Chrome auto-updates, so ensuring the browser is fully closed and relaunched applies the fix, and enterprises should push the build through their management channel. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Send security alert to all Chrome users; audit current Chrome version distribution using MDM or asset inventory tools. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-20 – Improper Input Validation
View allVendor StatusVendor
SUSE
Severity: Important| 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