EUVD-2026-93844
GHSA-98fw-v97v-pf83
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
ExploitServe crafted HTML/JS
-
ExecutionTrigger V8 type confusion
-
ImpactExecute code in renderer sandbox
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 | Exploitation requires the victim to use a vulnerable Google Chrome desktop build prior to 155.0.8059.39 and to load attacker-controlled content - specifically a crafted HTML page that drives the V8 JavaScript engine into a type-confusion state (CWE-843). The required user interaction (UI:R, visiting/rendering the page) is the primary limiting factor; no authentication or special privileges are needed (PR:N). A critical scope limitation: successful code execution is confined to the renderer/V8 sandbox per the description, so full host compromise additionally requires chaining a separate sandbox-escape vulnerability. Installations already updated to 155.0.8059.39 or later are not affected. |
| Impact | Multiple signals point to a genuine but not emergency-level priority. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates a network-reachable, low-complexity, unauthenticated flaw requiring only that a victim load a crafted HTML page - trivial to deliver via a malicious or compromised website. However, the SSVC decision framework from CISA reports Exploitation: none and Automatable: no, and there is no CISA KEV listing and no public POC, so there is no public exploit identified at time of analysis. The technical impact is rated 'total' by SSVC, consistent with the C:H/I:H/A:H impact metrics. A key mitigating nuance the raw score obscures: the description explicitly states code execution occurs 'inside the sandbox,' meaning a successful exploit of this single bug is confined to the V8/renderer sandbox and would require an additional sandbox-escape chain to achieve full host compromise - the CVSS C/I/A:H reflects worst-case in-renderer impact, not confirmed host takeover. Net assessment: a real, patch-worthy priority given Chrome's ubiquity and the ease of drive-by delivery, but not currently under active exploitation and not a standalone full-system RCE. |
| Exploit ScenarioDerived | An attacker hosts or compromises a website serving a crafted HTML page that triggers the V8 type-confusion flaw when a victim using a vulnerable Chrome build (prior to 155.0.8059.39) visits it. Because no authentication is required and complexity is low, a drive-by or phishing lure suffices to achieve arbitrary code execution within the renderer sandbox. No public exploit code is known, so an attacker would need to develop the exploit independently, and would require a separate sandbox-escape bug to break out onto the host. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Type confusion in the V8 JavaScript engine of Google Chrome prior to 155.0.8059.39 lets a remote, unauthenticated attacker execute arbitrary code inside the browser's renderer sandbox when a victim loads a crafted HTML page; the CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, so the sole prerequisite is that the victim renders attacker-controlled content in an unpatched desktop build. No public exploit code or active exploitation was identified at time of analysis, and CISA KEV does not list this CVE. The vendor-released patch is Chrome 155.0.8059.39, and installations already updated past that version are not affected. Because the impact is scoped to the sandbox (S:U) per the description, full host compromise would require chaining a separate sandbox-escape vulnerability.
RemediationAI
Upgrade Google Chrome to 155.0.8059.39 or later via the vendor-released stable channel update documented at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html; note that Chrome only activates the new binary after the browser is relaunched, so verify the running version at chrome://version rather than assuming the download completed the fix. Managed fleets should force the version through Chrome Browser Cloud Management, Google Update policy, or the organization's package manager and then confirm the version on endpoints. Where immediate upgrade is not possible, compensating controls carry real trade-offs and are not equivalent to patching: restricting browsing to trusted sites and blocking untrusted HTML/JavaScript reduces exposure to drive-by pages but is not a dependable barrier against a single crafted page; running the JIT disabled (for example --js-flags="--jitless") removes the optimizing-compiler attack surface this bug lives in at a substantial performance cost and is not a supported long-term configuration; and because the impact is confined to the renderer sandbox, keeping the OS and any later sandbox-escape fixes current is what prevents a renderer compromise from being chained into host compromise. No mitigation beyond the vendor update is indicated by the available data.
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
V8 is Chrome's JavaScript and WebAssembly engine, and its optimizing compilers (TurboFan/Maglev) rely on feedback about object shapes (maps/hidden classes) to emit specialized machine code. A type confusion (CWE-843) occurs when that type information is mishandled so code treats an object of one type as another, which in V8 typically yields out-of-bounds reads or writes in the renderer heap and, from there, arbitrary code execution within the renderer process. The SSVC assessment rates technical impact as total while noting exploitation is not observed and the flaw is not automatable, and the CVSS vector is network-reachable, low complexity, no privileges, and requires user interaction. Critically, the description states the code execution stays "inside the sandbox," so this is a renderer-level primitive, not by itself a host takeover; a second bug would be needed to escape the Chrome sandbox. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* for builds before 155.0.8059.39, with upstream root-cause detail tracked at https://issues.chromium.org/issues/567177599.
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
Network-delivered crafted page with no privileges (AV:N/PR:N), low complexity, but requires the victim to open the page (UI:R); in-sandbox code execution yields high C/I/A with unchanged scope.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Type confusion in V8 in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Organizations with Google Chrome desktop builds older than 155.0.8059.39 face a high-severity flaw that can let an unauthenticated remote attacker execute code inside the browser renderer sandbox when a user loads crafted web content, creating risk of data exposure or follow-on compromise if paired with a separate sandbox escape. Since Chrome is widely deployed across endpoints, VDI images, and remote-work devices, leadership should prioritize updating all affected systems to reduce exposure across the user base. No public exploit identified at time of analysis.
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