EUVD-2026-40655
GHSA-pwfh-44rh-2cj8
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote crafted page (AV:N), no auth (PR:N), but requires the victim to open the page (UI:R); renderer-sandbox code execution keeps scope unchanged (S:U) with full in-process C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Heap buffer overflow in V8 in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Remote code execution in Google Chrome's V8 JavaScript engine (versions prior to 150.0.7871.47) allows a remote attacker to run arbitrary code inside the renderer sandbox by luring a victim to a crafted HTML page. Exploitation requires user interaction (visiting a malicious page) but no authentication, and the flaw carries a CVSS 8.8 with high confidentiality, integrity, and availability impact. …
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 open or be redirected to an attacker-controlled HTML page in an unpatched Chrome (version < 150.0.7871.47) - this user interaction (CVSS UI:R) is the primary limiting factor, so there is no zero-click or server-side vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed but net to a real-but-not-emergency priority. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a malicious web page containing crafted JavaScript that triggers the V8 type-confusion/heap overflow, then drives a victim to it via phishing, a malicious ad, or a compromised site. When the victim's unpatched Chrome renders the page, the attacker gains arbitrary code execution inside the renderer sandbox, which they would typically pair with a separate sandbox-escape bug to reach the host. … |
| Remediation | Vendor-released patch: update Google Chrome to 150.0.7871.47 or later on all desktop platforms, then fully restart the browser so the new V8 build is loaded (Chrome auto-updates, but the update only takes effect after relaunch). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory Chrome versions across all endpoints; issue urgent security bulletin to all users with instructions to update to version 150.0.7871.47 or later. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Memory Corruption
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