EUVD-2026-105700
GHSA-f25p-44rc-59gq
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted HTML page
-
ExploitLure victim to visit
-
ExecutionTrigger DevTools memory corruption
-
ImpactExecute arbitrary code in sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 (earlier than 156.0.8078.47) and to visit an attacker-controlled crafted HTML page (UI:R), so there is no fully automatic drive-by against a non-browsing user. No authentication is required (PR:N). The flaw resides in the DevTools component, and successful code execution is confined to the browser sandbox (S:U) - a full host compromise would require chaining a separate sandbox-escape vulnerability, which is the primary factor limiting real-world severity and the reason for Google's 'Low' rating. |
| Impact | Signals conflict sharply and must be reconciled. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) yields an 8.8 'High' score driven by network reach, no privileges, and full C/I/A impact - but Google's own Chromium security rating is explicitly 'Low'. This divergence is the key fact: the CVSS impact metrics do not account for the description's critical qualifier that code executes 'inside the sandbox' (S:U, no scope change), so the attacker is confined to the renderer/DevTools sandbox rather than achieving host compromise, which is why the vendor rates it Low. No EPSS score was provided, there is no CISA KEV listing, and no public POC is referenced, so there is no evidence of active or imminent exploitation. Treat this as a routine browser-hardening patch, not an emergency: the 8.8 is a high-CVSS-but-lower-real-risk case because sandbox containment and the user-interaction requirement materially reduce practical impact. Patch via normal Chrome auto-update cadence. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page and lures a victim running a vulnerable Chrome build (prior to 156.0.8078.47) to visit it. Triggering the memory-corruption flaw in the DevTools component yields arbitrary code execution confined within the browser sandbox. No public exploit code has been identified at the time of analysis, and the attacker gains no privileges beyond the sandboxed context without chaining an additional sandbox-escape bug. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in the DevTools component of Google Chrome desktop builds prior to 156.0.8078.47 allows a remote attacker who convinces a victim to open a crafted HTML page to run arbitrary code within the browser sandbox. Although Google rates the Chromium security severity as Low, the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 8.8 because successful exploitation yields high confidentiality, integrity and availability impact inside the sandboxed renderer; no authentication is needed but user interaction (opening the page) is required. No public exploit code or confirmed active exploitation was identified at time of analysis, so the practical risk is tempered by the need for a separate sandbox-escape chain to reach the host.
RemediationAI
Upgrade Google Chrome to version 156.0.8078.47 or later, distributed through the standard stable channel release described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html; Chrome's auto-update normally applies this, but managed fleets should verify the version via enterprise policy or an inventory scan. If immediate upgrade is not possible, restrict use of DevTools on managed endpoints, keep browser instances isolated from sensitive credentials and sessions, and treat browsing of untrusted HTML as high risk - though none of these removes the underlying memory-corruption flaw. Note that a patch is available per vendor advisory, and no workaround fully substitutes for upgrading to 156.0.8078.47.
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 issue is a CWE-119 improper restriction of operations within the bounds of a memory buffer in Chrome DevTools, Chrome's built-in developer tooling. Memory-corruption flaws of this class typically involve out-of-bounds reads or writes in native code handling attacker-influenced input; here the corrupted memory lives in the DevTools surface exposed to a crafted HTML page, letting an attacker redirect execution flow and achieve arbitrary code execution. Because Chrome's multi-process architecture places this code inside the sandbox (S:U), code execution is contained to the compromised process and does not by itself yield host-level access - escaping the sandbox requires an independent vulnerability. EUVD enumerates affected builds as Chrome versions below 156.0.8078.47; the CPE-level product is Google Chrome on desktop platforms.
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 crafted page needs victim interaction (UI:R) but no auth (PR:N); code exec stays within the sandbox so scope is unchanged (S:U) despite high in-sandbox C/I/A.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in DevTools in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
Google Chrome desktop versions prior to 156.0.8078.47 contain a memory-corruption flaw in the DevTools component that could allow an attacker to execute code inside the browser sandbox if a user opens a crafted page. Because exploitation requires user interaction and no public exploit has been identified, the immediate organizational risk is contained, but unpatched browser fleets still represent a measurable exposure for data and productivity. Leadership should treat this as a patch-management priority for desktop Chrome rather than an active incident.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
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