Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage triggers use-after-free in Paint
-
ExecutionReclaim freed object with attacker data
-
ImpactExecute arbitrary code in 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 a victim to load attacker-controlled HTML in a vulnerable Chrome build (any version prior to 156.0.8078.73) - this user interaction (UI:R, navigating to a crafted page) is the primary limiting factor; there is no authentication requirement (PR:N) and no special non-default configuration is needed, as the Paint rendering component is core browser functionality. The decisive limit on impact is that successful exploitation yields code execution only inside the renderer sandbox, so full system compromise additionally requires a separate sandbox-escape vulnerability. Updating to 156.0.8078.73 or later removes the flaw. |
| Impact | This is a genuine priority, though its real-world severity is bounded by an important nuance in the description. The 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 remotely reachable, low-complexity, unauthenticated flaw requiring only that a victim load a crafted HTML page - the classic drive-by browser profile. However, the description explicitly scopes the outcome to 'execute arbitrary code inside the sandbox,' meaning this grants code execution only within the Chrome renderer process; full host compromise would require chaining a separate sandbox-escape bug, a limit the raw 8.8 does not convey (and consistent with S:U). Exploitation status: no public exploit identified at time of analysis - the CVE is not in CISA KEV and no PoC/exploit reference is supplied (the issues.chromium.org link is a tracker entry, typically access-restricted, not working exploit code). No EPSS score was provided, so statistical exploitation likelihood cannot be assessed here. The vuln.today decision label is 'this_week' (not act_now/emergency), aligning with a patched, high-severity renderer UAF that is not yet known to be exploited. Use-after-free in a browser (CWE-416) is a historically heavily weaponized bug class, so despite the absence of current exploitation signals, prompt patching within the stated window is warranted. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious markup/scripting that drives Chrome's Paint component into a use-after-free state; when a victim simply visits the page, the attacker achieves arbitrary code execution within the renderer sandbox. No authentication is needed and complexity is low, but the user must navigate to the page (UI:R) and the attacker gains only sandboxed execution unless paired with a sandbox escape. No public exploit code is identified at this time. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Use-after-free in Chrome's Paint rendering component allows a remote, unauthenticated attacker to execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in any Chrome build prior to 156.0.8078.73. The user-interaction requirement (UI:R, opening the page) is the main limiting factor; no credentials or non-default configuration are needed since Paint is core browser functionality, yet successful exploitation yields code execution only within the renderer sandbox, so full system compromise would additionally require a separate sandbox-escape flaw. Google rates the issue Chromium security severity High and has released a fixed build; no public exploit code or confirmed active exploitation was identified at time of analysis, and the vulnerability is prioritized for remediation this week.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.73 or later, distributed through the stable channel update described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html; because Chrome applies updates on restart, relaunching the browser after the update is required for the fix to take effect, and managed fleets should push the version through their update policy and verify the reported version. Organizations running Chromium-based browsers or embedded Chromium frameworks should confirm their vendors have rebased onto a Chromium build at or above the fixed milestone. Where an immediate update cannot be staged, the practical exposure limit is that this flaw provides code execution only inside the renderer sandbox, so maintaining the sandbox and keeping the browser isolated from sensitive credentials and local file access reduces the blast radius, though no configuration change removes the underlying use-after-free and updating remains the complete fix.
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 Paint, the Chromium component responsible for rasterizing and compositing page content during rendering. That class of defect means a heap object is released while a reference to it is still held and later dereferenced, which can hand an attacker control of reused memory inside the renderer process. The available sources do not describe the specific object lifetime or code path in Paint that is mishandled, so the exact trigger is not described in the available sources beyond loading attacker-controlled HTML. Because Paint is core browser functionality rather than an optional extension or non-default mode, exploitation does not depend on special configuration, and the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U) reflects a network-reachable, low-complexity attack that nonetheless requires the victim to open the crafted page. Chromium's multi-process architecture confines the resulting code execution to the sandboxed renderer, which is why scope is scored unchanged (S:U) and why a chained sandbox escape would be required for host compromise. The issue was reported through Google's Chrome CVE administration process and is tracked in the Chromium issue tracker under reference 572312175.
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; victim must open the page (UI:R); code runs in-sandbox so scope is unchanged (S:U) with high renderer-process C/I/A.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Paint in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
CVE-2026-118353 is a high-severity memory corruption flaw in Google Chrome's rendering engine that could allow an attacker to execute arbitrary code within the browser sandbox when a user visits a malicious or compromised website. While no active exploitation has been observed, the broad deployment of Chrome across the organization means a successful attack could impact any employee who browses the web, potentially leading to data theft or further compromise if chained with a sandbox escape. Leadership should prioritize patching to maintain the integrity of our endpoint defenses and reduce exposure to this credible threat.
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-111448
GHSA-87x2-8pvv-68m2
NVD
CVE.org
EPSS
Exploit-DB