Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious site
-
ExploitServe crafted HTML page
-
ExecutionTrigger input validation flaw in UI
-
ImpactExecute arbitrary code within renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
|
| Exploitation Conditions | Exploitation requires the victim to actively load an attacker-crafted HTML page in a vulnerable Chrome build (any version prior to 156.0.8078.47), consistent with UI:R in the CVSS vector - there is no fully passive or zero-click path described. No authentication is required (PR:N). The critical LIMITING factor is that successful exploitation yields code execution only INSIDE the renderer sandbox; achieving host-level compromise would additionally require a separate sandbox-escape vulnerability, which is not part of this CVE. This sandbox confinement, combined with the mandatory user interaction, substantially constrains real-world impact and aligns with the vendor's 'Low' severity rating. |
| Impact | This issue carries a notably conflicting risk profile. The input NVD/EUVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) yields a base score of 8.8 (High), implying full compromise of confidentiality, integrity, and availability. However, the vendor (Chromium) explicitly rates this as 'Low' severity, and the description states the arbitrary code executes INSIDE the sandbox - meaning the attacker gains code execution only within the confined renderer process, NOT on the host OS. A sandbox escape would be required for host compromise and is not described here, which largely explains the vendor's Low rating and directly contradicts the C:H/I:H/A:H impact scoring. Exploitation also requires user interaction (UI:R): the victim must visit an attacker-controlled page. On exploitation signals, no EPSS score, SSVC decision, KEV listing, or POC availability was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net assessment: despite the High CVSS, this is a lower-priority issue in practice - sandboxed-only impact plus required user interaction and no known exploitation. Patch promptly as part of routine Chrome updates, but it does not warrant emergency out-of-band response. Verify the impact scoring with the vendor, as the CVSS C/I/A:H ratings appear inconsistent with sandbox-confined execution and the Chromium 'Low' severity label. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page and lures a victim to visit it (via phishing link, malvertising, or a compromised site). When the victim's Chrome (prior to 156.0.8078.47) renders the page, improper input validation in a UI component is triggered, allowing the attacker to execute arbitrary code within the browser's renderer sandbox. No public proof-of-concept was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Sandbox-confined code execution in Google Chrome builds prior to 156.0.8078.47 lets a remote attacker who convinces a victim to open a crafted HTML page trigger improper input validation in the browser's UI layer and potentially run arbitrary code inside the renderer sandbox. No privileges are required (PR:N), but the attacker cannot act without the victim actively loading the page (UI:R), and any code that does run is contained by Chrome's sandbox - escaping to the host would require a separate, unrelated sandbox-escape flaw. The issue carries a notably conflicting risk profile: the raw 8.8 base score contrasts with Google's 'Low' Chromium severity rating and with our assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L, and no public exploit has been identified at time of analysis even though the fix is already shipping.
RemediationAI
Vendor-released patch: Chrome 156.0.8078.47 - upgrade to this stable build or later on every affected platform, following the version table in Google's advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html); most managed fleets can force the update through the browser's auto-update mechanism or an enterprise update policy, and a restart is required before the new build is active. Until the update is confirmed on a host, the practical compensating control is to constrain exposure to the user-interaction precondition - restrict browsing of untrusted or uncategorized sites via enterprise URL filtering or policy-driven extension allowlists, at the cost of user friction and administrative overhead - while keeping the renderer sandbox and Site Isolation enabled rather than disabling them to 'improve compatibility', since the sandbox is the only thing bounding this bug's impact. Note that because exploitation is confined to the renderer, endpoint detection opportunities are limited to renderer crash telemetry and anomalous child-process behaviour, so monitoring should focus on repeated renderer terminations tied to a specific site; disabling or loosening the sandbox as a workaround would convert a low-severity sandbox-confined issue into full host compromise and should not be considered. Verify patch compliance via browser version reporting before treating any endpoint as remediated.
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 root cause is CWE-20 (Improper Input Validation) in Chrome's user-interface layer - the code that renders and processes browser chrome rather than page content - where malformed input from a crafted HTML page is not adequately validated before use. The relevant security boundary is the Chromium renderer sandbox: a successful trigger yields arbitrary code execution only within the compromised renderer process, so confidentiality, integrity and availability effects are constrained (our assessment scores all three as Low), and host-level compromise presupposes a second, independent sandbox-escape vulnerability that this CVE does not cover. This is why the vendor assigned a Chromium security severity of 'Low' despite an unadjusted base score of 8.8, which assumes full C:H/I:H/A:H impact without accounting for sandbox containment. The affected code is fixed in the stable channel build 156.0.8078.47; EUVD records affected versions as Chrome builds below 156.0.8078.47, and the Chromium issue tracker entry (issues.chromium.org/issues/514078112) holds the restricted technical detail.
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 required user interaction (UI:R, PR:N); impacts reduced to Low because code execution is confined to the renderer sandbox without a host escape.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Improper input validation in UI in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Executive ViewAI
Google Chrome builds prior to 156.0.8078.47 contain a high-scored input-validation flaw that could permit code execution inside the browser's renderer sandbox when a user opens a crafted HTML page. The business exposure is broad because Chrome is widely deployed, but exploitation requires user action and any resulting code remains constrained by the sandbox; no public exploit has been identified at time of analysis. Leadership should care because unpatched browser fleets remain a recurring endpoint risk, and a vendor fix is already available for coordinated rollout.
Apply vendor patch.
Threat Intelligence Overview
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
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
EUVD-2026-105705
GHSA-3xrg-7wrw-jf4g
NVD
CVE.org
EPSS
Exploit-DB