EUVD-2026-105741
GHSA-6qpf-c2g6-jvgp
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger memory corruption in Chrome Core
-
ExecutionExecute arbitrary code in renderer sandbox
-
ImpactChain sandbox escape for host impact
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 a crafted HTML page in an affected Google Chrome build (prior to 156.0.8078.47) - this is user interaction (UI:R), but it is low-friction drive-by interaction with no authentication (PR:N) and works against default configurations. The key LIMITING factor, per the vendor, is that resulting code execution is confined to the renderer sandbox: the attacker cannot reach host data, credentials, or the OS without separately exploiting a sandbox-escape vulnerability. This sandbox confinement is why Chromium rates the issue 'Low' despite the 8.8 CVSS. |
| Impact | Signals are mixed and should be weighed carefully. 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 network-reachable, low-complexity, unauthenticated memory-corruption flaw requiring only that a victim load a crafted HTML page - the classic drive-by browser profile. However, the description explicitly states code execution occurs 'inside the sandbox,' and Google's own Chromium rating is 'Low,' which is a meaningful contradiction to the 8.8 score: without a chained sandbox escape, attacker-controlled code is confined to the renderer process and cannot directly reach host data or the OS, so the real-world C/I/A to the host is far lower than the vector implies. No EPSS score was supplied, the CVE is NOT in CISA KEV, and no public exploit (POC) was identified in the provided data, so there is no evidence of active or imminent exploitation. Net assessment: patch promptly as part of routine Chrome updating given ubiquity and the drive-by vector, but this is not an emergency 'patch-now' priority on the strength of the data available - the sandbox confinement and low vendor severity temper the high CVSS. EPSS/KEV/POC absence is noted as missing data, not as proof of safety. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious HTML/JavaScript that triggers the Core memory-corruption bug when rendered. A victim running a vulnerable Chrome build (before 156.0.8078.47) visits the page and the attacker gains arbitrary code execution within the renderer sandbox. No public exploit code was identified at time of analysis, and code execution remains confined to the sandbox unless chained with 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
Memory corruption in Google Chrome's Core component before version 156.0.8078.47 allows a remote, unauthenticated attacker to execute arbitrary code inside the browser sandbox when a victim loads a crafted HTML page. Exploitation requires user interaction but no credentials, and the vendor rates the issue Chromium severity Low because the resulting code execution is confined to the renderer sandbox rather than the host OS. No public exploit code has been identified at time of analysis.
RemediationAI
Update Google Chrome to version 156.0.8078.47 or later; the vendor has released a patch. On managed endpoints, verify the installed version and force an update through Chrome's enterprise update policy, then restart the browser so the new binary is active. See the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. If immediate patching is not possible, keep Chrome's renderer sandbox and site isolation enabled (disabling them would expand impact if the memory corruption is triggered), restrict browsing to trusted sites or use a separate hardened browser profile for untrusted content, and monitor for renderer crashes that could indicate exploitation attempts; these are temporary risk reductions, not fixes.
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-113288 is a CWE-119 improper restriction of operations within the bounds of a memory buffer in Chrome's Core component. The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H describes a network-reachable flaw that requires the victim to render a crafted HTML page, after which memory corruption can be turned into arbitrary code execution within the renderer's sandbox. Because the sandbox blocks direct access to host files, credentials, and OS resources, practical impact depends on chaining with a separate sandbox-escape vulnerability; Google accordingly assigns Chromium severity Low despite the high base score. No CPE data was supplied, but the affected product is Google Chrome desktop builds prior to 156.0.8078.47 per the Chrome Releases advisory.
Know when Chrome gets its next vulnerability
- 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 gives AV:N/AC:L/PR:N, victim must open the page so UI:R; scope stays unchanged (S:U) as code runs confined to the sandboxed renderer process with full compromise of it.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Core 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 releases before 156.0.8078.47 carry a memory-corruption flaw that can allow code execution inside the browser sandbox when a user opens a malicious page. The exposure is broad across the Chrome user base but is gated by user interaction, and sandbox confinement limits-though does not remove-the potential for downstream business disruption. Security leadership should treat this as a time-bound patching priority for browsing-heavy roles and verify fleet compliance quickly.
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.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Exploit-DB