EUVD-2026-105711
GHSA-qr48-c8jx-pq4w
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
DeliveryBrowser renders malicious content
-
ExploitTrigger memory corruption in SignIn
-
ExecutionExecute arbitrary code in renderer sandbox
-
ImpactSandbox-contained code execution
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 | Requires a victim using Google Chrome prior to 156.0.8078.47 to actively open or navigate to an attacker-crafted HTML page (UI:R), so there is no fully automated or drive-by-free remote exploitation. No authentication is required (PR:N). Critically, successful exploitation yields code execution confined to the renderer sandbox per the vendor description - escaping to the host requires chaining a separate sandbox-escape vulnerability, which is the primary factor limiting real-world impact and the reason Chromium rated this 'Low' despite the 8.8 CVSS figure. |
| Impact | Signals conflict and must be weighed carefully. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) paints this as a high-severity, network-reachable, unauthenticated memory-corruption flaw needing only a single user action. However, Google/Chromium independently rated this 'Low' severity, and the description states code execution occurs 'inside the sandbox' - meaning the flaw does NOT by itself escape Chrome's renderer sandbox or compromise the host OS, which is why the vendor rating diverges sharply from the mechanical CVSS number. This is the key tension: CVSS treats renderer-contained RCE as full C/I/A High, while in Chrome's threat model a sandboxed renderer compromise is low-impact without a chained sandbox-escape bug. No EPSS score was provided in the input, so exploitation probability cannot be quantified. The CVE is NOT in CISA KEV and no public exploit code is referenced. Net assessment: patchable and worth routine prioritization, but it is a high-CVSS / low-real-risk issue in isolation - a vendor-rated 'Low' sandboxed bug, not an urgent actively-exploited threat. Verify the sandbox-containment scope against the Chromium issue tracker before deprioritizing, since memory-corruption bugs are frequently chained. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page and lures a victim running a pre-156.0.8078.47 Chrome build to visit it (e.g., via phishing link or malvertising). When the page is rendered, the SignIn component mishandles memory, letting the attacker execute arbitrary code - but only within the constraints of the renderer sandbox, so a separate sandbox-escape bug would be required for full host compromise. No public exploit code is identified 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 the SignIn component of Google Chrome releases prior to 156.0.8078.47 lets a remote, unauthenticated attacker potentially execute arbitrary code - but only inside the renderer sandbox - after convincing a victim to open a crafted HTML page. Google's Chromium team rated this 'Low' severity even though the CVSS 3.1 base score is 8.8, because the corruption yields in-sandbox code execution and host compromise would require chaining a separate sandbox escape. No public exploit code has been identified and the issue is not in CISA KEV, although the vendor has already shipped a fixed build; the conflict between the high numeric score and the Low vendor rating is the main judgement call for prioritisation.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later via the Stable channel update described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html (Chrome typically auto-updates; verify the version under Settings > About Chrome and relaunch to apply). Because exploitation requires the victim to load an attacker-crafted HTML page, the most effective compensating controls before patching are to restrict rendering of untrusted content: disable or tightly scope JavaScript/site isolation exceptions, enforce enterprise URL allow-lists for the SignIn flow, and block known-bad hosts at the proxy - noting that URL filtering only reduces exposure and does not remove the memory-safety defect. Organisations that cannot update immediately should reduce the attack surface by disabling the browser's account sign-in/sync integration via the GoogleSigninAllowed / SyncDisabled enterprise policies, at the trade-off of losing profile sync and single sign-on convenience, and should isolate Chrome into a disposable VM or restricted browser session so that any in-sandbox code execution has no persistence path. Continue to rely on the renderer sandbox as the primary impact limiter - do not treat a successful in-sandbox primitive as host compromise - but monitor for chained sandbox-escape activity, and re-check the Chromium issue tracker for the public write-up once the restriction is lifted. Chromium-derived browsers should be updated to the corresponding vendor build that incorporates upstream 156.0.8078.47.
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 a CWE-119 improper restriction of operations within the bounds of a memory buffer - a classic buffer/memory corruption issue - located in Chrome's SignIn code, the browser-side component that handles account sign-in and profile authentication flows in the Chromium multi-process architecture. Per the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) the attack surface is network-reachable and needs no credentials, but requires user interaction: the victim must navigate to or open a malicious HTML page that triggers the out-of-bounds memory operation. Because the compromise is scoped to the renderer sandbox (S:U, with the vendor explicitly noting the attacker runs 'inside the sandbox'), confidentiality and integrity impact against the renderer process is high, yet converting it into full host-level code execution demands a second, independent sandbox-escape bug. Affected software is Google Chrome builds below 156.0.8078.47 on desktop channels as tracked by ENISA EUVD; the underlying defect is in the Chromium open-source codebase, meaning downstream Chromium-derived browsers inheriting that version range may also need vendor confirmation. The Chromium issue tracker entry is the authoritative root-cause reference and is currently access-restricted until most users have patched.
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 (AV:N) needing only a page visit (UI:R, PR:N); sandboxed RCE keeps S:U but still yields High C/I/A within the renderer context.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in SignIn 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: Low)
Executive ViewAI
Google Chrome deployments older than 156.0.8078.47 carry a high-scored but vendor-downgraded security defect that could let an attacker execute code within the browser’s isolated rendering environment after a user opens a malicious page. Employees who use Chrome for business browsing are the primary exposure group, and the availability of a fixed build means the residual risk is largely a patch-management problem. Leadership should prioritize rapid update verification because Chrome is widely deployed and the high CVSS score creates audit and reporting attention despite the sandbox limitations.
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