EUVD-2026-111432
GHSA-p6mv-27j3-mfcc
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitBrowser parses malicious HTML markup
-
ExecutionTrigger memory corruption (CWE-119)
-
ImpactExecute arbitrary code inside 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 or navigate to an attacker-crafted HTML page in Google Chrome desktop prior to 156.0.8078.73; no authentication is required (PR:N) and it works against default configurations, but it does require user interaction (UI:R) to load the malicious content. A key limiting factor is scope: the description states code execution is confined to the renderer sandbox (S:U), so full host compromise would additionally require a separate sandbox-escape vulnerability. The specific feature or markup that triggers the corruption is not described in the available sources. |
| Impact | This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 High) indicates a remote, low-complexity, unauthenticated memory-corruption bug (CWE-119) that is reachable by any visitor to a malicious page, which is why the impact metrics are all High. However, two signals temper the raw score: the description explicitly states code execution occurs 'inside the sandbox' (S:U, no scope change), so a successful exploit alone yields renderer-level code execution and still requires a separate sandbox-escape chain for full host compromise; and exploitation requires user interaction (UI:R), i.e. the victim must open attacker-controlled HTML. On the threat-intel side the picture is thinner: there is no EPSS score, no CISA KEV listing, and no confirmed public exploit in the provided data - the only Chromium-tracker reference (issues.chromium.org/568730797) is Google's bug record, typically access-restricted, not a PoC. The vuln.today decision label is 'this_week' rather than act_now/emergency, consistent with a patched browser RCE that is not known to be exploited. Net: patch on the normal fast browser-update cadence; treat as high because of ubiquitous deployment, but current evidence does not show active or imminent mass exploitation. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that triggers the memory-corruption condition in Chrome's HTML handling, then lures a victim to visit it (link, ad, or malvertising). On an unpatched Chrome build prior to 156.0.8078.73, rendering the page can corrupt memory and potentially execute arbitrary code within the renderer sandbox. No public exploit code is identified in the provided data, and the specific trigger is not described in the available sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Memory corruption in Chrome's HTML handling lets a remote attacker potentially execute arbitrary code inside the renderer sandbox when a victim loads a crafted HTML page in Google Chrome desktop builds prior to 156.0.8078.73. The CVSS vector shows unauthenticated network delivery (PR:N, AV:N) but requires the user to navigate to the attacker's page (UI:R), and the description scopes any code execution to the sandbox (S:U), so full host compromise would need a separate sandbox escape. No public exploit code or in-the-wild exploitation has been identified at time of analysis, and Google rates the issue Chromium security severity High with a vendor fix already published in 156.0.8078.73.
RemediationAI
Update Google Chrome desktop to 156.0.8078.73 or later; Google has released a patch for this issue and the fix is delivered through the standard stable channel update described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_0562499947.html. Given the this_week priority, schedule the version bump through normal browser update mechanisms and verify the installed build on managed endpoints, since no fixed version exists below 156.0.8078.73 and the vulnerable component is the renderer that handles every HTML page a user opens. No vendor-documented workaround or configuration-level mitigation is specified in the available sources, and the practical risk reduction before patching comes from the built-in renderer sandbox, which confines any successful code execution and means host compromise would require an additional sandbox-escape bug; that confinement is not a substitute for the update.
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 as CWE-119 (improper restriction of operations within the bounds of a memory buffer) in the HTML component of Google Chrome, meaning malformed or specially crafted markup drives the renderer outside an intended memory boundary and corrupts memory. Because the corruption occurs in the renderer - the sandboxed process that parses and renders web content - the description limits the demonstrated impact to code execution inside that sandbox; escaping to the host operating system is not part of this issue and would require chaining a second, separate sandbox-escape vulnerability. The relevant technology is Chromium's HTML parsing/rendering pipeline as shipped in Chrome desktop before 156.0.8078.73; the specific feature, element or markup construct that triggers the corruption is not described in the available sources, and no CPE strings were supplied to narrow the affected platform further beyond the EUVD version range. Exploitation requires the victim to open or navigate to an attacker-crafted HTML page in an affected build, with no authentication (PR:N) and default configurations, but user interaction (UI:R) is mandatory to load the content.
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
Remotely reachable via a crafted page with no auth (AV:N/PR:N) but requires the victim to load it (UI:R); code execution stays within the sandbox (S:U) with full renderer C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in HTML in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
Google Chrome desktop versions prior to 156.0.8078.73 contain a high-severity memory corruption flaw that could allow an attacker to execute code within the browser's sandbox when a user visits a malicious webpage. While no active exploitation has been observed, this vulnerability poses a significant risk to the organization's workforce, as a successful attack could lead to data compromise or further network intrusion, requiring immediate remediation.
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