Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted web page
-
DeliveryServe malicious HTML to browser
-
ExploitTrigger use-after-free in Compositing
-
ExecutionReclaim freed object, hijack control flow
-
ImpactExecute arbitrary code within renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
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 an affected Google Chrome build prior to 156.0.8078.47 and to load attacker-controlled web content (UI:R) - no authentication or prior privileges are needed (PR:N). The defining limiting factor is that successful code execution is confined to the renderer SANDBOX (scope Unchanged); to escape the sandbox and compromise the host, an attacker must chain this with a separate sandbox-escape vulnerability. No special victim-side configuration is required, so default Chrome installations rendering the malicious page are exposed, but the attack cannot succeed without user navigation to the crafted page. |
| Impact | Signals are mostly aligned toward a genuine but bounded priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) describes a remote, unauthenticated, low-complexity attack that only requires a victim to load a crafted HTML page - a realistic drive-by condition for a browser. However, the most important mitigating signal is embedded in the description itself: code execution is 'inside the sandbox' and the CVSS scope is Unchanged (S:U), so a successful exploit is contained to the renderer sandbox and would require a separate sandbox-escape chain to achieve full host compromise. This is consistent with Chromium's own 'Medium' severity rating, which is notably LOWER than the aggregate CVSS of 8.8 - a conflict worth flagging: the 8.8 reflects full C/I/A loss within the renderer, while Google's Medium rating reflects the sandbox containment that limits real-world blast radius. No EPSS score was provided, so exploitation probability cannot be quantified. The CVE is NOT on CISA KEV and no POC is referenced, so this is not confirmed active exploitation. No SSVC decision data was supplied. Net: a credible memory-corruption flaw in a ubiquitously-deployed product that should be patched promptly via normal browser auto-update cadence, but absent a paired sandbox escape it is not an immediate full-system-compromise emergency. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing specially crafted HTML/content that triggers the use-after-free in Chrome's Compositing component when rendered. A victim who merely visits the page (UI:R) has attacker-controlled code executed within the browser's renderer sandbox. No public exploit is referenced, and full host compromise would additionally require chaining a separate sandbox-escape vulnerability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Use-after-free in Google Chrome's Compositing component allows a remote attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in a build prior to 156.0.8078.47. The issue is unauthenticated from the network perspective but requires user interaction (UI:R), and the independent assessment bounds impact to sandbox code execution because scope is Unchanged; host compromise would require chaining a separate sandbox escape. Vendor-released patch: 156.0.8078.47; no public exploit identified at time of analysis.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later (vendor-released patch: 156.0.8078.47). Use Chrome's built-in auto-update or enterprise update enforcement, verify the installed version via chrome://version, and block or isolate Chrome installations below that build. Where immediate upgrade is not possible, reduce exposure by restricting navigation to trusted sites and isolating browsing in a disposable or remote environment, accepting reduced usability as the trade-off; disabling compositing is not a documented workaround and may break rendering. Consult the Chrome advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the Chromium issue at https://issues.chromium.org/issues/534956586 for vendor details.
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
CVE-2026-113081 is a CWE-416 use-after-free in Chromium's Compositing component, the rendering pipeline that assembles page layers before display. A use-after-free means an object is freed while still referenced; subsequent use can corrupt memory and, in this case, permit arbitrary code execution within the Chrome renderer process. Because the assessed vector has scope Unchanged and the impact is confined to the renderer sandbox, the defect does not by itself grant host-level compromise; an attacker would need a second, separate sandbox-escape vulnerability to break out. The affected technology is Google Chrome builds prior to 156.0.8078.47; no CPE identifiers were supplied, so platform-specific narrowing beyond the vendor's affected Chrome builds is not possible from the available data.
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 crafted page with no auth (AV:N/PR:N) but requires user to load it (UI:R); scope Unchanged because execution stays in the renderer sandbox, with full C/I/A loss there.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Compositing 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: Medium)
Executive ViewAI
A high-severity memory corruption flaw in Google Chrome's Compositing component (CVE-2026-113081) allows a crafted web page to run attacker-supplied code inside the browser's renderer sandbox on any machine running a Chrome build older than 156.0.8078.47, and because exploitation requires the user to visit a malicious or compromised page, every employee who browses the web with an unpatched browser is a potential entry point. Impact is currently bounded to the renderer sandbox - full host compromise would need a second, separate sandbox-escape vulnerability - and no public exploit has been identified, so leadership should treat this as a manageable but time-sensitive fleet hygiene issue rather than an active incident.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-105599
GHSA-5c28-48hj-v3c2
NVD
CVE.org
EPSS
Exploit-DB