EUVD-2026-105734
GHSA-5rf8-55px-6859
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
ExploitServe crafted HTML to browser
-
ExecutionTrigger memory corruption in BrowserTag
-
ImpactExecute arbitrary code within 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 load attacker-controlled crafted HTML in a vulnerable Google Chrome build prior to 156.0.8078.47 (CVSS UI:R confirms required user interaction - visiting/rendering the page). No authentication or special privileges are needed (PR:N). The principal limiting factor is that resulting code execution is contained within the browser sandbox (Scope:Unchanged); reaching the underlying host requires an additional, separate sandbox-escape vulnerability not covered by this CVE, which is why the vendor rates the security severity Low. Chrome's silent auto-update mechanism further limits the exposure window on default desktop installations. |
| Impact | Signals are mixed and must be weighed carefully. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8 High) describes a remote, unauthenticated, low-complexity flaw needing only that a victim visit a crafted HTML page - a classic drive-by profile. However, the vendor (Chromium) rates the security severity 'Low', and the critical mitigating factor is Scope:Unchanged combined with the description's own wording: code execution is 'inside the sandbox', not a sandbox escape. The renderer/component sandbox is specifically designed to contain exactly this class of memory corruption, so without a chained sandbox-escape bug the real-world impact is far lower than the 8.8 score implies. This is the key conflict: CVSS treats in-sandbox code execution as full C/I/A High, while the vendor's 'Low' rating reflects that the sandbox remains the trust boundary. There is no EPSS score, no CISA KEV listing, and no public exploit (POC) indicated in the input, so no public exploit identified at time of analysis. Net assessment: patch as part of normal Chrome auto-update hygiene given ubiquity, but this is a high-CVSS, low-real-priority issue absent an accompanying sandbox-escape chain - not an emergency. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that triggers the BrowserTag memory corruption when rendered. A user is lured to the page (phishing link, malvertising, or compromised site); on load, the attacker potentially achieves arbitrary code execution confined to the browser sandbox. No public exploit code was identified in the provided data, and a separate sandbox-escape bug would be required to reach the host OS. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in the BrowserTag component of Google Chrome before 156.0.8078.47 lets a remote attacker who convinces a victim to load a crafted HTML page corrupt memory within the renderer and potentially execute arbitrary code inside the browser sandbox; no credentials or privileges are required, only that the victim renders the page (CVSS PR:N/UI:R). The resulting code execution is scope-limited to the sandbox - escaping to the host requires a separate sandbox-escape bug not covered by this CVE - which is why Google rates the Chromium security severity Low even though the generic CVSS base score computes to 8.8. No public exploit code or confirmed active exploitation was identified at time of analysis, and Chrome's silent auto-update mechanism shortens the exposure window on default desktop installations. Signals are mixed and must be weighed carefully: the numeric severity is high while the practical post-exploitation impact is constrained by the sandbox.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 156.0.8078.47 or later - the fix ships in the stable channel release described at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html, and default desktop installs will pick it up automatically, so verify the build via chrome://version and force a relaunch if the update is pending. For managed fleets, push the version through Google Update/enterprise update policies (UpdateDefault/Update policy or your software deployment tooling) rather than relying on user-driven restarts, since a pending relaunch leaves the browser exploitable. Organizations running Chromium derivatives should track their vendor's rebase to the equivalent Chromium milestone, as they will lag behind Google's fix. Until patched, keep the renderer sandbox and site isolation enabled - do not launch with --no-sandbox or disable site isolation, as that converts an in-sandbox bug into host-level compromise - and consider restricting browsing of untrusted or user-supplied HTML to patched hosts or disposable/remote-browsing environments, accepting reduced usability. Deploying content filtering or blocking unknown high-risk sites reduces exposure but is imperfect and adds false-positive friction; there is no configuration toggle that disables BrowserTag without breaking normal page rendering.
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 classic CWE-119 improper restriction of operations within the bounds of a memory buffer, occurring in Chrome's BrowserTag implementation - a Chromium component involved in tagging/labelling browser-level objects. Because the defect lives in memory handling reachable from parsed attacker-supplied HTML, successful exploitation typically proceeds through heap or object corruption: the attacker shapes memory layout via the crafted page and then redirects control flow within the renderer process. Chromium's multi-process architecture and site isolation confine the corrupted context to the sandboxed renderer, so the CVE's practical ceiling is in-sandbox code execution with the victim's renderer privileges; chaining to the OS requires an independent sandbox escape. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H reflects network reachability, low attack complexity, no privileges, mandatory user interaction (page load), unchanged scope, and high confidentiality/integrity/availability impact inside the sandboxed context - the divergence from Google's Low Chromium severity rating stems directly from that sandbox containment.
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 requires only a victim visit (AV:N/AC:L/PR:N/UI:R); impact is high but contained within the sandbox, so Scope stays Unchanged.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in BrowserTag 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
Unpatched Google Chrome installations carry a high-CVSS browser code-execution risk that is constrained by Chrome's renderer sandbox and requires a user to open crafted web content. A vendor patch (156.0.8078.47) is available and no public exploit identified at time of analysis; while the generic CVSS is 8.8, the practical impact is bounded by the sandbox and Google's Low Chromium severity rating. Leadership should care because the exposure sits in a user-facing browser workflow, so risk reduction depends on rapid endpoint update discipline.
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