Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryDeliver malicious compositing input
-
ExploitTrigger improper input validation flaw
-
ExecutionEscape browser sandbox
-
ImpactExecute arbitrary code on host
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 load attacker-controlled content in Chrome - the CVSS UI:R and the description's 'crafted HTML page' mean a user must visit a malicious or compromised web page; there is no click-beyond-navigation or authentication requirement (PR:N). The flaw resides in the Compositing component and affects default configurations of Chrome versions prior to 156.0.8078.47, so no special feature toggle is needed. The primary LIMITING factor is the required user interaction (navigating to the page) and the fact that the outcome is described as 'potentially' executing code outside the sandbox, implying exploitation may not be fully reliable; patched builds (156.0.8078.47+) are not affected. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, 9.6 Critical) describes a highly dangerous condition: a network-reachable, low-complexity, unauthenticated sandbox escape with full confidentiality, integrity and availability impact, requiring only that a victim load a page. There is a notable CONFLICT in the data: the vendor (Chromium) rated this 'Medium' severity, while the CVSS base score is 9.6 Critical - this gap likely reflects Chromium's internal severity methodology (which weighs exploitability and real-world reachability of the compositing bug) versus the mechanical CVSS scope-change calculation; defenders should not treat the 9.6 as fully vendor-endorsed. No EPSS score, no CISA KEV listing, and no public exploit (POC) were provided, so there is no evidence of active or imminent exploitation. Given the ubiquity of Chrome, the correct posture is prompt patch deployment on severity-and-reach grounds, but this is not currently a 'drop everything' actively-exploited emergency. In short: high theoretical severity and enormous attack surface, but no exploitation signal - prioritize patching broadly without assuming in-the-wild use. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious HTML that triggers the improper input validation flaw in Chrome's Compositing component. A victim running an unpatched Chrome (prior to 156.0.8078.47) simply visits the page, and the attacker potentially achieves arbitrary code execution outside the browser sandbox on the victim's host. No public exploit code was identified at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Improper input validation in Google Chrome's Compositing component before 156.0.8078.47 can let a remote, unauthenticated attacker achieve code execution outside the browser sandbox when a victim loads a crafted HTML page. The CVSS 3.1 score is 9.6 Critical (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H), but exploitation depends on user interaction and the vendor describes the code-execution outcome as potential rather than guaranteed. Google has released a fixed build, and no public exploit code has been identified at time of analysis.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later and restart the browser so the patched binary is loaded, then verify the version via chrome://version. For managed fleets, push the vendor update through Chrome Enterprise policies or update tooling and block or warn on versions below 156.0.8078.47. The vendor advisory is https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. Because exploitation requires a victim to load attacker-controlled HTML, reducing exposure to untrusted web content and enforcing prompt restart/update are temporary compensating measures until patching completes, though neither replaces the fixed build; no vendor workaround beyond updating is identified.
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
Chrome's Compositing component combines rendered page layers into the final browser output, and the flaw is classified as CWE-20 improper input validation. The supplied description states that crafted HTML can trigger the issue and potentially execute arbitrary code outside the sandbox, which is consistent with the CVSS scope-change metric (S:C) and a boundary crossing from normally sandboxed web content into a more privileged context. The vector AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H indicates network reachability, low attack complexity, no authentication requirement, mandatory user interaction, and high confidentiality, integrity, and availability impact; the vendor's Chromium severity is Medium even though the supplied CVSS score is 9.6 Critical.
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:C/C:H/I:H/A:H
Remote crafted page with no privileges (AV:N/PR:N/AC:L) but requires navigation (UI:R); sandbox escape changes scope (S:C) and code execution on the host yields full C/I/A:H.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Improper input validation in Compositing in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome's Compositing component carries a critical-severity input-validation flaw affecting Chrome builds before 156.0.8078.47, creating a path for a remote, unauthenticated attacker to achieve code execution outside the browser sandbox when a user loads a crafted HTML page. The organizational exposure is broad because Chrome is widely deployed, and a sandbox escape can turn a browsing event into endpoint compromise; leadership should prioritize patching, though no public exploit has been identified at time of analysis and a vendor fix is available.
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-105506
GHSA-f4vg-x2wq-9xvr
NVD
CVE.org
EPSS
Exploit-DB