EUVD-2026-105602
GHSA-c7wj-w487-q5hx
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious HTML page
-
ExploitBrowser renders crafted content
-
ExecutionTrigger memory corruption in Core
-
ImpactExecute arbitrary code in 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 open attacker-controlled content: a crafted HTML page rendered by a vulnerable Chrome build (any version prior to 156.0.8078.47) - this is the UI:R requirement in the CVSS vector. No authentication or special configuration is needed (PR:N), and default Chrome installations are affected. The principal limiting factors are (1) required user interaction (victim must navigate to the malicious page) and (2) sandbox containment - the flaw yields code execution only 'inside the sandbox' (S:U), so without a separate sandbox-escape chain the attacker does not gain host-level code execution. |
| Impact | The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 8.8 High) describes remote, unauthenticated, low-complexity exploitation requiring only that a victim open a crafted HTML page. However, this conflicts with the vendor's own rating: Google/Chromium classified the severity as Medium, reflecting that the description states code execution is 'inside the sandbox' (S:U, no confirmed sandbox escape), which materially limits real-world impact - a renderer-only compromise normally requires a chained sandbox-escape bug to become full host code execution. No EPSS score was provided, the CVE is NOT in CISA KEV, and no public POC is referenced, so there is no public exploit identified at time of analysis. Net assessment: this is a patch-promptly browser flaw rather than an emergency - the high CVSS is driven by the network/no-auth/low-complexity metrics, but the Medium vendor rating and sandbox containment temper the practical risk. Note the discrepancy explicitly: NVD-style CVSS 8.8 (High) versus Chromium 'Medium' severity - the sandbox qualifier is the reconciling factor. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious HTML that triggers the memory-corruption flaw in Chrome's Core component when rendered. A user is lured (e.g., via phishing or malvertising) into visiting the page, and the attacker potentially achieves arbitrary code execution within the renderer sandbox. No public exploit code is known, and meaningful host compromise would typically require chaining an additional 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 allows a remote, unauthenticated attacker to execute arbitrary code inside the browser sandbox when a victim loads a crafted HTML page in any desktop build prior to 156.0.8078.47. The assessed CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 High) reflects low-complexity exploitation gated only by the user-interaction requirement, with sandbox containment (S:U) meaning a standalone compromise yields renderer-level code execution rather than direct host takeover. No public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, and no EPSS score was supplied in the source feed; Google rates the flaw Medium under its own Chromium severity scale, and a vendor patch is available.
RemediationAI
Vendor-released patch: upgrade Google Chrome desktop to 156.0.8078.47 or later - the fix ships in the Stable Channel update documented at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the underlying Chromium issue is https://issues.chromium.org/issues/537465180. Standard practice is to let the built-in updater apply the build and then fully restart the browser (chrome://settings/help confirms the running version); enterprise fleets should force the version through Google Update / Chrome Browser Cloud Management policy (UpdateDefault, TargetVersionPrefix) and verify compliance before relaxing any interim controls. Because the defect sits in core memory handling rather than in a single toggleable feature, there is no true workaround - the practical compensating controls are to keep the renderer sandbox and Site Isolation enabled (both default; do not disable them for troubleshooting during this window), and, for high-risk user populations only, to set DefaultJavaScriptSetting to block script execution or route untrusted browsing through a hardened alternate browser, at the cost of breaking most modern web applications. Network-layer domain and proxy filtering offers marginal value against attacker-hosted pages created after the fact and should not be treated as a substitute for patching.
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 classified CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), the classic out-of-bounds read/write class in which a length or index calculation is not validated against the actual size of an allocated buffer. In Chrome's multi-process architecture, HTML parsing, DOM manipulation and JavaScript execution occur in a heavily sandboxed renderer, so a memory-safety bug in the browser's Core layer is reachable from untrusted web content but its immediate payoff is code execution confined to the renderer sandbox. Achieving host-level compromise would require chaining this defect with a separate sandbox-escape vulnerability; none is referenced in the available intelligence, and Google's own advisory groups the fix into a routine Stable Channel desktop update covering the Chrome 156.0.8078.47 build. The upstream bug is tracked as Chromium issue 537465180 and was credited to chrome-cve-admin@google.com. No CPE dictionary entries were supplied in the feed, so affected builds are identified by the vendor version string (all Chrome desktop releases below 156.0.8078.47) rather than by formal platform-specific CPE URIs.
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 HTML needs victim navigation (AV:N/UI:R) with no auth (PR:N); code execution is confined to the renderer sandbox (S:U) with high renderer-process C/I/A impact.
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 potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome desktop builds prior to 156.0.8078.47 contain a memory-corruption flaw in the browser's Core component that lets an attacker run code inside the browser sandbox simply by getting a user to open a malicious web page. Because Chrome is broadly deployed across the workforce, any employee browsing the web is a potential entry point, and a successful attack could expose data and credentials handled in the browser session. Leadership should care less about the technical mechanics than about the breadth of exposure and the fact that remediation is a routine browser update that can be driven centrally.
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