EUVD-2026-105428
GHSA-5vf6-c8vx-x4c7
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitMalicious frame content processed by Chrome
-
ExecutionTrigger memory corruption in Frames
-
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 use an affected Chrome build (prior to 156.0.8078.47) and to actively load attacker-controlled HTML/frame content - the CVSS UI:R reflects this mandatory user interaction (visiting a page), which is the primary limiting factor. No authentication is required (PR:N) and default configurations are vulnerable; no special Chrome feature or non-default setting is named as a prerequisite. The critical scope limit is that successful exploitation yields code execution only within the Chromium renderer sandbox (S:U, 'inside the sandbox'), so full host compromise requires chaining with a separate sandbox-escape vulnerability. |
| Impact | This is a genuine high-priority patch item, though not a drop-everything emergency. The provided CVSS:3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) indicates network-reachable, low-complexity, unauthenticated exploitation requiring only that a victim open a crafted HTML page - a trivially satisfiable condition for a web browser. The memory-corruption (CWE-119) flaw in Chrome's Frames component is rated High by Chromium's own severity scale and a patch is confirmed available. Mitigating the risk somewhat is a key detail in the description: code execution is 'inside the sandbox' with Scope:Unchanged, meaning this alone does not escape Chromium's renderer sandbox to compromise the host - it typically must be chained with a separate sandbox-escape bug to achieve full system compromise. Notably, NO EPSS score, NO CISA KEV listing, and NO public POC are present in the provided data, so there is no evidence of active exploitation: this is 'no public exploit identified at time of analysis.' The signals are therefore consistent rather than conflicting - high theoretical severity and ubiquitous attack surface, but no current exploitation evidence. Absence of EPSS/KEV data should not be read as low risk, only as unconfirmed; browser memory-corruption bugs are routinely targeted, so prompt patching is warranted. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page (or injects malicious frame content into a compromised/advertised site) and lures a Chrome user into visiting it. The crafted HTML triggers memory corruption in Chrome's Frames handling, letting the attacker execute arbitrary code within the renderer sandbox; to fully compromise the host it would need to be chained with a sandbox-escape vulnerability. No public exploit code is identified in the provided data at 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 Chrome's Frames component allows a remote attacker who convinces a victim to open a crafted HTML page to achieve arbitrary code execution inside the Chromium renderer sandbox. All Chrome builds prior to 156.0.8078.47 are affected, and exploitation requires no authentication - the only real barrier is the mandatory user interaction of loading attacker-controlled frame content (CVSS UI:R). Google rates the issue High severity (Chromium) and lists it as fixed in the 156.0.8078.47 stable release; no public exploit code has been identified at time of analysis, and the practical impact is bounded by the sandbox, so full host compromise would require chaining with a separate sandbox-escape flaw.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later via the stable-channel update described in https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html; most installs will auto-update, but verify the running build under chrome://version and force a relaunch, since Chrome applies updates only after restart. ChromeOS devices should be moved to the corresponding fixed stable release per http://chromereleases.googleblog.com/2026/10/stable-channel-update-for-chromeos_01150416531.html, and managed fleets can enforce the timeline through enterprise update policies (e.g., pinning the target version and shortening the relaunch grace period) - the trade-off being forced browser restarts for users. Because exploitation needs the victim to load crafted frame content, interim risk reduction is limited but real: restrict browsing to trusted sites or isolate untrusted web access in a separate low-privilege environment, keeping in mind that Site Isolation and the renderer sandbox already contain this bug to renderer-level code execution and are therefore controls you should not weaken (disabling Site Isolation or launching with --no-sandbox would turn a sandboxed RCE into host compromise). Blocking or filtering untrusted embedded frames at a proxy reduces exposure at the cost of breaking legitimate third-party content, and disabling scripting for untrusted origins is a heavier trade-off that breaks most modern sites.
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), which in Chromium's multiprocess architecture typically manifests as an out-of-bounds read/write, heap corruption, or type confusion in the renderer process while parsing and laying out frame content. Because the corrupted memory lives in the renderer, a successful exploit first defeats control-flow integrity within that process, yielding code execution at the renderer's privilege level rather than the OS level - the CVSS scope of Unchanged (S:U) accurately reflects this containment. The attack surface is the ordinary web-content path: a victim merely visiting a page or embedding a malicious subframe triggers the vulnerable frame-handling logic, which is why the vector carries AV:N/L/PR:N but UI:R. The advisory credits Google's internal chrome-cve-admin tracking and the Chromium issue tracker entry 535749304; as is standard for Chrome memory-safety bugs, technical specifics are restricted until the majority of users have updated, so defenders should treat the Frames subsystem as the affected area rather than a single named API.
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 needs victim interaction (UI:R, AV:N, PR:N); code runs inside renderer sandbox without escape so Scope Unchanged, with high C/I/A impact on the browser process.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in Frames 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: High)
Executive ViewAI
Google Chrome versions prior to 156.0.8078.47 contain a high-severity memory-corruption flaw in the Frames component that could allow a crafted web page to execute code inside the browser's renderer sandbox on an affected user's machine. Because Chrome is widely deployed across the workforce, this creates broad exposure to malicious web content, though the sandbox limits the immediate blast radius and no public exploit has been identified at time of analysis. Leadership should treat this as an urgent patch-management priority to reduce risk across all endpoints.
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