EUVD-2026-105544
GHSA-x5x5-8qw4-jc8p
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted web page
-
ExploitServe malicious HTML to Chrome
-
ExecutionTrigger memory corruption in Search
-
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 a victim running Google Chrome prior to 156.0.8078.47 to load an attacker-crafted HTML page (CVSS UI:R - user interaction via navigating to the page is mandatory); no authentication or special privileges are needed (PR:N). The key limiting factor is sandbox containment: the description states code executes 'inside the sandbox', so this flaw alone does not compromise the host OS and would require chaining with an independent sandbox-escape for full system takeover. Default Chrome configurations are affected - no non-default feature or setting is called out as a prerequisite. |
| Impact | The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8 High) describes a network-reachable, low-complexity, unauthenticated memory-corruption flaw requiring only that a victim load a crafted HTML page. However, two signals temper this: (1) Google/Chromium rated the security severity 'Medium', not High, a notable discrepancy with the 8.8 NVD score; and (2) the description explicitly states code execution occurs 'inside the sandbox', meaning this bug alone does not escape Chrome's renderer sandbox to compromise the host - it would need to be chained with a separate sandbox-escape to achieve full RCE, which is consistent with the S:U (scope unchanged) metric. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. Net: this is a patch-promptly browser bug (ubiquitous product, no user auth, only UI:R gating it) but is NOT a confirmed-exploited emergency; the 8.8 overstates standalone impact given sandbox containment, and the absence of EPSS/KEV/POC suggests it is not yet weaponized. Verify the severity gap (NVD 8.8 vs Chromium Medium) against the vendor advisory before prioritizing above other High-score issues. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that triggers the memory-corruption bug in Chrome's Search component when the victim visits it. Because the CVSS vector specifies UI:R, the victim must actively navigate to the attacker-controlled page; successful exploitation yields arbitrary code execution confined to the renderer sandbox, which would then require a separate sandbox-escape to affect the underlying system. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in Chrome's Search component lets a remote, unauthenticated attacker achieve code execution inside the browser sandbox when a victim simply loads a crafted HTML page in any Chrome build prior to 156.0.8078.47 (CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 High). Because the flaw is explicitly scoped to code execution 'inside the sandbox', it does not by itself grant host-level compromise and would need to be chained with a separate sandbox escape for full system takeover, though an in-sandbox primitive already exposes credentials, session data, and files reachable by the renderer. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, but Google has shipped a vendor patch and the required user interaction (a single page visit) keeps the practical bar to exploitation low for targeted campaigns.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later, as documented in the Chrome stable channel advisory (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html) and tracked in the Chromium issue https://issues.chromium.org/issues/513226023; the update must be applied through the browser's built-in updater or an enterprise package deployment, and Chrome should then be relaunched because the fix only takes effect after a full restart of the browser process (an open, un-restarted session remains exploitable). Until the fleet is confirmed on the patched build, restrict browsing to trusted sites and block untrusted or uncategorized web content, accepting the loss of general web access that this entails; note that disabling JavaScript or the Search-related features reduces but does not eliminate attack surface because the corrupted parsing path is reachable from ordinary page loads. Enterprises using Chrome Enterprise policies should verify the deployed version via version reporting and force a relaunch, since staged rollouts can leave hosts on the vulnerable build for days. There is no separate vendor workaround published for this issue - patching is the only complete fix - and because code execution is contained inside the sandbox, defenders should also monitor renderer crash clusters and anomalous post-renderer behavior as an indicator of attempted exploitation.
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) in Chrome's Search component, a browser-side subsystem that processes page-derived data and therefore parses attacker-influenced input inside the renderer's memory space. Classic bounds-handling defects of this class produce out-of-bounds reads/writes that corrupt heap or object metadata, which an attacker can steer into controlled memory writes and ultimately arbitrary code execution within the compromised renderer - the classic first stage of a two-stage Chrome exploit chain. The CVSS vector AV:N/AC:L/PR:N/UI:R confirms the attack is network-delivered, requires no credentials or privileges, and needs only that the target navigate to the malicious page (UI:R); the sandbox boundary constrains impact to the renderer rather than the host OS. Google's own severity rating for the underlying Chromium issue is Medium even though the NVD base score is 8.8 High, reflecting the difference between a standalone renderer compromise and a full-chain escape. Affected per CPE/EUVD data: Chrome releases below 156.0.8078.47.
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 requires victim navigation (UI:R) and no auth (PR:N); code execution is confined to the renderer sandbox so scope is unchanged (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 Search 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 builds prior to 156.0.8078.47 contain a high-severity memory-corruption flaw in the Search component that can allow an attacker to execute code inside the browser sandbox after a user simply visits a crafted page. Because Chrome is widely deployed and exploitation requires only a single page view, unpatched users could expose credentials, session data, and files reachable by the browser; leadership should treat this as a priority patching event even though full host takeover would require an additional sandbox escape.
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