Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger improper input validation in Chromoting
-
ExecutionExecute arbitrary code
-
ImpactImpact confined to Chrome 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 | Requires a victim running Google Chrome prior to 156.0.8078.47 to actively visit an attacker-controlled crafted HTML page (UI:R), which exercises the Chromoting / Chrome Remote Desktop input-validation path. The decisive LIMITING factor is that resulting code execution is confined to the browser sandbox - the description describes no sandbox escape, so an attacker does not obtain host-level code execution from this flaw alone. User interaction (navigation to the malicious page) is mandatory, and the issue is remediated by updating to 156.0.8078.47 or later. |
| Impact | Signals conflict sharply and must be reconciled before prioritizing. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, unauthenticated, low-complexity flaw with full High impact, which on its face looks urgent. However, the description explicitly states code execution occurs 'inside the sandbox' and Google's own Chromium security team rated the severity as Low - a strong indicator that real-world impact is contained by the renderer/sandbox boundary and does not by itself yield host compromise. No EPSS score was provided, the vulnerability is NOT in CISA KEV, and no public POC is referenced, so there is no public exploit identified at time of analysis. Net assessment: this is a patch-on-normal-cadence browser issue, not an emergency. The headline 8.8 overstates practical risk because the full-High impact metrics ignore the sandbox confinement that Chromium's 'Low' rating reflects; absent a chained sandbox-escape (not described here), an attacker gains only sandbox-confined execution. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page and lures a Chrome user (version prior to 156.0.8078.47) into visiting it. The crafted HTML triggers improper input validation in the Chromoting (Chrome Remote Desktop) component, allowing the attacker to execute arbitrary code, but only within the browser sandbox. No public exploit code is referenced, and successful exploitation requires user interaction (UI:R) to load the attacker's page. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Sandbox-confined arbitrary code execution in Google Chrome's Chromoting (Chrome Remote Desktop) component affects versions prior to 156.0.8078.47; a remote, unauthenticated attacker can trigger it only if a victim opens a crafted HTML page (UI:R). Chromium rates the flaw Low, and no public exploit or CISA KEV entry was identified at time of analysis, so NVD's 8.8 score overstates risk: execution does not escape the browser sandbox, and our assessment is C:L/I:L/A:L. Updating to 156.0.8078.47 or later removes the flaw.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later; allow the built-in updater to complete and verify the version at chrome://version, or deploy the fixed package through your software-management tooling. See the Chrome stable channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html) and Chromium issue 562960821 for details. If Chromoting/Chrome Remote Desktop is not required, reduce exposure by disabling the Chrome Remote Desktop host and remote-access connections through enterprise policy, accepting the loss of remote-support functionality; this is a compensating control, not a fix, and does not address the underlying input-validation flaw. Restricting users from opening untrusted HTML pages is impractical as a primary mitigation, and the sandbox limits but does not eliminate the need to patch.
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
Chromoting is the protocol and component behind Chrome Remote Desktop, handling input from remote sessions and web-exposed surfaces. CWE-20 (Improper Input Validation) indicates the component failed to validate crafted input delivered through an HTML page, enabling code execution in the Chromoting context. The CVSS vector is AV:N/AC:L/PR:N/UI:R/S:U, so exploitation is remote and unauthenticated but requires victim navigation; scope is unchanged, and the description explicitly limits execution to inside the sandbox, with no sandbox escape described. NVD scored C:H/I:H/A:H (8.8), but the independent assessment and Chromium's Low severity rating treat impact as C:L/I:L/A:L because host compromise is not demonstrated. EUVD lists Chrome versions before 156.0.8078.47; no CPE strings were provided. References include the Chrome stable channel advisory and Chromium issue 562960821.
Know when the next one hits your stack
- 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, no auth, low complexity, but user must visit a page (UI:R) and execution is sandbox-confined with no described escape, so impacts are Low rather than High, matching Chromium's 'Low' rating.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Improper input validation in Chromoting 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 installations that have not reached 156.0.8078.47 carry a code-execution flaw in the Chromoting/Chrome Remote Desktop component, but the impact is constrained by the browser sandbox and requires a victim to open a crafted HTML page. No public exploit identified at time of analysis, and the likely confidentiality, integrity, and availability effects are limited, making this primarily a browser patch-hygiene issue. Leadership should care because delayed updates across a broad Chrome estate can create avoidable exposure and compliance noise even when the direct technical consequence is narrow.
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.
EUVD-2026-105750
GHSA-62w3-f5cw-w4j5
NVD
CVE.org
EPSS
Exploit-DB