EUVD-2026-105710
GHSA-cq45-g55f-fm7r
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage triggers memory corruption in Model component
-
ExecutionCorrupt heap/memory to hijack control flow
-
ImpactExecute arbitrary code within renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
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 load attacker-controlled content in Chrome prior to 156.0.8078.47 (UI:R - the user must visit or render a crafted HTML page); it cannot be triggered purely remotely without that interaction. No authentication is required (PR:N) and it works against default configurations - there is no special feature flag or non-default setting named in the description. The decisive LIMITING factor is that code execution is confined to the renderer sandbox (Scope:Unchanged): achieving host/system compromise requires chaining an additional sandbox-escape vulnerability, which is why the vendor rates the security severity 'Low' despite the 8.8 base score. |
| Impact | Signals conflict and must be weighed carefully. NVD scores this 8.8 (High) with vector AV:N/AC:L/PR:N/UI:R, implying a low-complexity, unauthenticated, network-reachable code-execution bug requiring only that a victim open a crafted page. However, Google/Chromium explicitly rates the security severity as 'Low,' and the description confirms code executes INSIDE the renderer sandbox (CVSS Scope:Unchanged) - not on the host. This is the key reconciling fact: a sandboxed RCE alone does not compromise the user's system without a separate sandbox-escape chain, which explains the large gap between the 8.8 NVD base score and the vendor's Low rating. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active or imminent exploitation. Treat this as a standard browser-patch priority: worth deploying promptly via normal Chrome update channels, but not an emergency given sandbox confinement and the absence of exploitation signals. Verify the sandbox-containment assumption against the vendor advisory before deprioritizing. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page (or injects malicious content into a page the victim already trusts) that triggers the memory-corruption flaw in Chrome's 'Model' component when rendered. A victim who visits the page has attacker-controlled code executed within the browser's renderer sandbox; full host compromise would require chaining a separate sandbox escape. 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
Memory corruption in the Chrome 'Model' component allows a remote attacker who convinces a victim to render a crafted HTML page to execute arbitrary code inside the browser's renderer sandbox in Chrome versions prior to 156.0.8078.47. No authentication is required, but exploitation depends on user interaction (the victim must visit or load the attacker-controlled page), and because the resulting code execution is confined to the sandbox, full host compromise would require chaining a separate sandbox-escape bug - which is why Google assigned this only a 'Low' Chromium security severity despite the 8.8 base score. No public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Vendor-released patch: Google fixed this in Chrome 156.0.8078.47, published via the stable channel update at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html (tracker: https://issues.chromium.org/issues/523248913); upgrade to that build or later, and verify the version under chrome://settings/help or the About Chrome menu, since Chrome's updater may lag on managed endpoints. For fleets, enforce the minimum version through enterprise policy (for example the version pinning / auto-update policies in Chrome Browser Cloud Management) and inventory any Chromium-embedded applications that must rebase onto 156.0.8078.47. Until patching is complete, compensating controls with known trade-offs include: keeping Site Isolation enabled (limits cross-site data exposure if a renderer is compromised, at some memory cost), disabling or restricting the feature area exposed by the 'Model' component via enterprise policy where a policy exists (reduces attack surface but may break ML/on-device model functionality), and blocking or sandboxing untrusted HTML content at the network/proxy layer or via strict content policies (adds latency and can break legitimate web applications). Note the sandbox confines any successful exploitation to the renderer process, so maintaining an up-to-date browser and OS to prevent a follow-on sandbox escape is the key residual-risk control, and users should treat unexpected renderer crashes as a possible exploitation signal.
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 defect is classified as CWE-119 (improper restriction of operations within the bounds of a memory buffer), the classic memory-safety class that in Chrome/Chromium renderer code typically manifests as an out-of-bounds read or write in native code reachable from parsed or rendered web content. The affected component is listed as 'Model' in the Chrome stable channel release notes, and the flaw is reachable from a crafted HTML page, meaning the vulnerable path is exercised in the renderer process that handles attacker-supplied markup. Modern Chrome isolates renderers in a multi-process sandbox, so the primitive here yields arbitrary code execution within that sandboxed process (CVSS Scope:Unchanged), not direct operating-system-level code execution. The relevant build boundary is Chrome 156.0.8078.47, per the vendor advisory and the ENISA EUVD entry (EUVD-2026-105710) tracking 'Chrome 156.0.8078.47 <156.0.8078.47'; no CPE strings were supplied with the source data, so exact platform/OS coverage should be taken from the Chrome release blog. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) matches: network-delivered content, no privileges, but a mandatory user-interaction step, with high confidentiality and integrity impact scoped to the sandboxed component.
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 delivery (AV:N) needing no auth (PR:N) but victim rendering (UI:R); sandbox confinement keeps Scope Unchanged, with high C/I/A within the renderer process.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Model 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: Low)
Executive ViewAI
Google Chrome versions prior to 156.0.8078.47 contain a memory-corruption flaw in the Model component that could allow a crafted webpage to execute code within the browser's renderer sandbox. Employees using unpatched Chrome are affected, but exploitation requires user interaction and remains sandbox-confined unless chained with a separate escape; no public exploit identified at time of analysis. Leadership should prioritize rapid browser updates because Chrome is widely deployed, while recognizing that a vendor patch is already available and no active exploitation has been confirmed.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Exploit-DB