Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger use-after-free in Compositing
-
ExecutionReclaim freed object via heap manipulation
-
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 open an attacker-controlled crafted HTML page in Chrome (CVSS UI:R) - there is no server-side or passive trigger. No authentication or prior privileges are needed (PR:N), and the flaw is reachable against default Chrome configurations prior to 157.0.8103.38 with no special feature or configuration prerequisite named in the description. The principal limiting factor is that resulting code execution is confined to the renderer sandbox, so impactful host compromise additionally requires a separate sandbox-escape not covered by this CVE; the specific object lifecycle and trigger within the Compositing component is not described in the available sources. |
| Impact | This is a genuine high-priority patch item, though not an emergency. The CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U) describes a network-reachable, low-complexity, unauthenticated flaw whose only gating factor is user interaction - the victim must open a crafted HTML page. The SSVC framework confirms Technical Impact: total but Exploitation: none and Automatable: no, and there is no CISA KEV listing, so there is no evidence of active exploitation at this time. No EPSS score was supplied in the input, so exploitation probability cannot be quantified here. The references include a Chromium issue-tracker entry (issues.chromium.org/567321055), which is typically access-restricted and is NOT verified as working exploit code; combined with the absence of any KEV/POC confirmation, this points to a patched, responsibly-disclosed bug rather than one under broad attack. One important caveat the description states explicitly: code execution occurs INSIDE the sandbox, meaning a successful exploit alone does not yield host compromise without an additional sandbox-escape - this materially tempers real-world severity relative to the raw 8.8. The vuln.today decision label is 'this_week', consistent with a serious but not actively-exploited memory-corruption flaw in ubiquitous software. |
| Exploit ScenarioDerived | A remote attacker hosts or injects a crafted HTML page that triggers a use-after-free in Chrome's Compositing component when a victim visits it (UI:R / crafted HTML page). Successful exploitation yields arbitrary code execution confined to the renderer sandbox, which would then require a separate sandbox-escape to affect the host. No public, verified exploit code is identified at the time of analysis; a restricted Chromium issue reference exists but is not confirmed working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Use-after-free in Google Chrome's Compositing component allows a remote attacker to achieve arbitrary code execution inside the renderer sandbox by getting a victim to open a crafted HTML page in any build prior to 157.0.8103.38. The attacker needs no credentials or prior access (PR:N) but must win user interaction (UI:R), and the resulting execution is confined to the sandbox - full host compromise would require a separate sandbox escape not covered by this CVE. Vendor-released patch: 157.0.8103.38; no public exploit code has been identified at time of analysis, no KEV listing is present, and CISA SSVC records exploitation as none, which places this as a this-week remediation item rather than an emergency.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 157.0.8103.38 or later, per the stable channel advisory at https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html; use the browser's built-in update flow (chrome://settings/help) or the platform package manager, then relaunch so the new binary is actually running - an updated install that is never restarted remains exposed. Because exploitation requires the victim to load a crafted HTML page (UI:R) and no privilege escalation is needed (PR:N), prioritize the update on endpoints with broad web browsing exposure, and confirm the deployed version rather than relying on update-check success. The supplied sources document no configuration workaround or feature toggle that removes the Compositing code path, and note that the code execution this CVE yields is sandbox-confined, so host-level impact additionally depends on an independent sandbox escape; treat the version upgrade, not a mitigation, as the complete fix. The referenced Chromium issue (567321055) is access-restricted and provides no public technical detail to guide interim mitigations.
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 flaw is a use-after-free (CWE-416) in Chromium's Compositing code - the layer that assembles painted content into the frames the browser presents, and therefore one of the more heavily exercised paths in the renderer. Use-after-free means a heap object is released while a reference to it is still reachable; subsequent use of that dangling reference can let an attacker redirect control flow through corrupted memory. The specific object, its lifecycle, and the precise conditions that free and then reuse it are not described in the available sources, so the exact trigger beyond 'load a crafted HTML page' is unconfirmed. CPE data (cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*) with a wildcard version and no OS component indicates the advisory covers Chrome across platforms; the affected range is every build below 157.0.8103.38. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms network reachability, no privileges required, mandatory user interaction, and unchanged scope - the security boundary that limits blast radius is the renderer sandbox, not the CVE itself.
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 gives AV:N/AC:L/PR:N, but victim must open the page so UI:R; renderer-sandbox code execution is high-impact and unchanged scope, so C/I/A:H, S:U.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Compositing in Google Chrome prior to 157.0.8103.38 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
A high-severity use-after-free flaw in Google Chrome's Compositing component could let an attacker run arbitrary code within the browser's renderer sandbox if a user simply opens a malicious web page. All Chrome installations below version 157.0.8103.38 are affected, meaning the broader workforce's browsing activity carries exposure; however, code execution is confined to the sandbox and no active exploitation has been observed, so leadership should prioritize standard-paced patching rather than emergency response.
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-116525
GHSA-7xfv-9mfr-pcw9
NVD
CVE.org
Vulnrichment
Exploit-DB