EUVD-2026-89384
GHSA-f5fp-62g2-jm9q
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
DeliveryServe crafted HTML/JavaScript
-
ExploitTrigger V8 type confusion
-
ExecutionExecute arbitrary code in renderer sandbox
-
ImpactStage sandbox escape for full compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the victim to browse to attacker-controlled content: exploitation needs a crafted HTML page rendered by an unpatched Chrome desktop build prior to 154.0.8037.92 (UI:R user interaction). No authentication or special privileges are required (PR:N), and default Chrome configurations are affected since V8 executes JavaScript on any page. The key limiting factor is that code execution is confined to the renderer sandbox (S:U, 'inside the sandbox') - full host compromise requires chaining an additional sandbox-escape vulnerability. Users on the fixed 154.0.8037.92 or later, or with JavaScript disabled for untrusted origins, are not exposed. |
| Impact | This is a genuine high-priority vulnerability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 8.8) describes a network-reachable, low-complexity, unauthenticated flaw requiring only that a victim visit a malicious page - the classic drive-by RCE profile for browser V8 type-confusion bugs. Type confusion in V8 is Google's own most heavily exploited Chrome bug class historically. No EPSS score, no CISA KEV listing, and no public POC were provided in the input, so exploitation status is 'no public exploit identified at time of analysis'; the absence of KEV means this should NOT be described as actively exploited despite the dangerous bug class. The one signal that tempers raw urgency is S:U - the arbitrary code executes inside the Chrome renderer sandbox (as the description explicitly says 'inside the sandbox'), so a second sandbox-escape bug is needed for full host compromise. Given ubiquitous Chrome deployment, a vendor patch is already available, and the well-understood exploitability of V8 type confusion, patching should be prioritized even without confirmed in-the-wild activity. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted JavaScript that triggers a V8 type-confusion condition. A victim running an unpatched Chrome (before 154.0.8037.92) simply visits the page (UI:R - user interaction of browsing), and the attacker gains arbitrary code execution within the renderer sandbox. No public exploit code was identified at time of analysis, but V8 type-confusion bugs are historically among the most reliably weaponized Chrome flaws. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 29, 2026
Type confusion in the V8 JavaScript engine in Google Chrome prior to 154.0.8037.92 lets remote attackers execute arbitrary code inside the renderer sandbox by luring a victim into opening a crafted HTML page. Exploitation is unauthenticated (CVSS:3.1/AV:N/AC:L/PR:N/UI:R) but requires user interaction - the victim must render the attacker's page - and because V8 runs JavaScript on essentially every page, default desktop configurations are exposed. Impact is scored 8.8 High (C:H/I:H/A:H) with the important caveat that code execution is confined to the sandbox, so full host compromise requires chaining a separate sandbox-escape bug; no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch is available as Chrome 154.0.8037.92.
RemediationAI
Vendor-released patch: Google Chrome 154.0.8037.92 - upgrade to this version or later (see the stable channel advisory at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_01807488085.html and the bug entry at https://issues.chromium.org/issues/560233248). The most reliable path is to let Chrome's auto-update mechanism install the release and then fully restart all browser processes, since a running instance continues to execute the vulnerable V8 code until restarted; verify the running build via chrome://version. Organizations should also enforce a minimum version through enterprise update policies or their MDM/patch-management tooling, and push out the fix to Chromium-based forks (Edge, Brave, Opera, Electron-based clients) as soon as those vendors rebase on 154.0.8037.92 or newer. Where immediate upgrade is impossible, the effective compensating control is to prevent untrusted JavaScript from reaching V8: set site-level JavaScript blocking to deny script execution on untrusted origins, or route browsing through a policy-enforced blocklist - the trade-off is that this severely degrades most modern web applications and is not a substitute for patching. Keeping site isolation enabled (the default) does not prevent the type confusion but does bound the damage by containing code execution to the renderer sandbox, so it should not be disabled; disabling the sandbox or running with --no-sandbox would remove that containment and should be avoided. Because exploitation requires the victim to open a crafted HTML page, email/web gateway filtering of untrusted links, hardened browser profiles restricted to sanctioned sites, and user awareness for unsolicited links reduce exposure, though none of these are reliable standalone mitigations against a memory-corruption bug of this class.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a CWE-843 type confusion in V8, Chrome's JavaScript and WebAssembly engine, where an object is treated as a type it is not - a memory-safety defect that can corrupt internal object representations and give an attacker control over a value later used for memory access. In practice, such confusion arises in V8's optimizing tiers (Sparkplug/Turbofan/Maglev) and inline-cache/feedback-vector handling, where speculative assumptions about object maps or element kinds are assumed to hold; a mismatch between the assumed and actual type during JIT-compiled code execution can be converted into out-of-bounds read/write primitives and, from there, into arbitrary code execution within the renderer. This is a classic Chrome renderer-side primitive, and the practical ceiling is the sandbox boundary: exploitation gains code execution in the compromised renderer process only, so escaping Chrome's site-isolation/sandbox architecture requires an independent second vulnerability. The single affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* (all versions before the fixed release), tracked as EUVD-2026-89384, and the CVSS vector (PR:N, UI:R) confirms no authentication is needed but a victim must visit attacker-controlled content.
Know when Chrome gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Remote drive-by via crafted page (AV:N/AC:L/PR:N/UI:R); code exec stays within renderer sandbox so S:U with full C/I/A impact on that process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Type confusion in V8 in Google Chrome prior to 154.0.8037.92 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome versions prior to 154.0.8037.92 are affected by a high-severity type confusion in the V8 JavaScript engine that allows a remote, unauthenticated attacker to execute code inside the browser's renderer sandbox when a user visits a crafted web page. Because V8 processes JavaScript on virtually every page and Chrome is widely deployed across the organization, standard desktop configurations are exposed. No public exploit code or active exploitation has been identified, and a vendor patch is available, but the broad attack surface and potential for chaining with a sandbox-escape flaw warrant prompt remediation.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
VulDB
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Exploit-DB