Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-delivered via web page (AV:N), no special setup required (AC:L), no attacker credentials needed (PR:N), victim must visit page (UI:R), sandbox boundary limits scope change (S:U), full triad impact within renderer process (C:H/I:H/A:H).
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
Type confusion in V8 in Google Chrome prior to 151.0.7922.169 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Type confusion in V8, Chrome's JavaScript engine, enables arbitrary code execution inside the Chrome renderer sandbox on any platform (Windows, macOS, Linux) when a user visits an attacker-controlled HTML page. All Chrome releases prior to 151.0.7922.169 are affected; Google has released the patched stable-channel build. …
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 | The sole prerequisite is that the victim visits an attacker-controlled or compromised web page using an unpatched Chrome version (prior to 151.0.7922.169) on any desktop platform. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | CVSS 8.8 correctly captures the theoretical severity - network-reachable, low complexity, no authentication, user-interaction-only gate - but several signals pull the practical priority downward. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a webpage containing crafted JavaScript that triggers the V8 type confusion bug; a victim running an unpatched Chrome version visits the page, causing Chrome to mishandle an internal object type and allowing the attacker to execute arbitrary code within the Chrome renderer process. From that foothold, a chained sandbox escape exploit would be needed to reach the underlying operating system. … |
| Remediation | Update Google Chrome to version 151.0.7922.169 or later, which is available via Chrome's built-in auto-update or from the stable-channel release announcement at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0826575033.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify all Chrome versions deployed across the organization and notify users of the availability of patched version 151.0.7922.169. …
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: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-61236
GHSA-fv7q-ch7q-75v6