EUVD-2026-105435
GHSA-vrq3-7rqp-p99j
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML/XML page
-
ExploitBrowser parses malformed XML
-
ExecutionTrigger memory corruption in XML handler
-
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 load attacker-controlled content - a crafted HTML page containing malformed XML that reaches Chrome's XML parsing path (UI:R, user interaction required); it cannot be triggered without the user navigating to or rendering the malicious page. The vulnerability affects Google Chrome desktop builds prior to 156.0.8078.47. A key limiting factor: code execution is confined to the renderer sandbox (CVSS scope Unchanged), so full host compromise additionally requires a separate sandbox-escape vulnerability. No authentication is needed (PR:N), and no special non-default Chrome configuration is indicated by the description. |
| Impact | Signals are mostly consistent toward a genuine but second-tier priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) describes a remote, low-complexity, unauthenticated memory-corruption bug that nonetheless requires user interaction (visiting a crafted page). Critically, the description states code execution occurs INSIDE the Chrome sandbox - meaning this flaw alone does not yield full host compromise and would need to be chained with a separate sandbox-escape to achieve attacker goals on the underlying OS; the CVSS scope is correctly Unchanged (S:U), reflecting this containment. There is no CISA KEV listing and no public exploit was identified at time of analysis, so this is 'no public exploit identified at time of analysis.' EPSS is not provided in the input, so exploitation probability cannot be quantified. Net: a real, patch-now browser RCE primitive of the kind routinely abused in exploit chains, but absent KEV/POC/EPSS evidence it is not a confirmed active-exploitation emergency - prioritize via normal Chrome auto-update cadence. Note the input Tag 'RCE' is technically accurate only in the in-sandbox sense; treat 'arbitrary code execution' as sandbox-constrained unless a chained escape is present. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malformed XML that triggers the memory-corruption bug in Chrome's XML handling when a victim browses to it. Successful exploitation yields arbitrary code execution within the renderer sandbox, which a real-world attacker would then pair with a sandbox-escape bug to reach the host. No public proof-of-concept was 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 Chrome's XML handling allows a remote attacker to potentially execute arbitrary code inside the renderer sandbox by convincing a victim to open a crafted HTML page; the flaw affects Google Chrome desktop builds prior to 156.0.8078.47 and requires user interaction (the page must be loaded or rendered), with no authentication needed. Google rates the Chromium security severity as High and lists the issue privately in its tracker, and the vendor has released 156.0.8078.47 as the fixed build. Impact is bounded by the renderer sandbox: because the CVSS scope is Unchanged, code execution is confined to the sandboxed process and full host compromise would additionally require a separate sandbox-escape bug. No public exploit code or confirmed active exploitation was identified at time of analysis.
RemediationAI
Upgrade Google Chrome to 156.0.8078.47 or later; this is a vendor-released patch (Vendor-released patch: 156.0.8078.47) delivered through the standard Chrome stable channel, so most users should simply relaunch the browser to apply the pending update and verify via chrome://version. Managed fleets should push the update through their normal mechanism (Google Update policies such as UpdateDefault/Allow updates, or the enterprise MSI/PKG deployment at the fixed version) and confirm the reported version on endpoints, since a browser left running for weeks will not pick up the fix. Release details are in the vendor advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and the technical report is at https://issues.chromium.org/issues/553121395 (restricted while the fix propagates). No configuration-level workaround removes the flaw: XSS Auditor-style filters and content-security-policy tuning do not prevent a crafted page the user deliberately visits from reaching the XML parser, and blocking XML MIME types at a proxy reduces but does not eliminate exposure while breaking legitimate XML-delivered content. The practical compensating control, if patching must be staged, is to keep Site Isolation enabled (default) so renderer compromise stays sandboxed, and to prioritize the update for users who routinely browse untrusted or user-generated HTML; note that sandboxing limits but does not eliminate the risk, since a chained sandbox escape would convert this into full host compromise. Enterprise allow-listing of Chromium extensions or alternative browsers should not be treated as mitigation, as those builds may lack the fix.
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 root cause class is CWE-119 (improper restriction of operations within the bounds of a memory buffer), i.e. an out-of-bounds write or read in native parsing code that can be manipulated into memory corruption. The vulnerable surface is Chrome's XML parsing path: when a document is served as XML, Blink's XML document parser handles it (delegating the low-level tokenizing/parsing work to libxml2 in the Chromium architecture), so malformed markup, deeply nested or entity-heavy documents, or inconsistent encoding declarations can drive the parser into an unsafe state. Successful corruption of parser-owned heap structures can, in principle, be turned into controlled execution within the renderer process; the practical ceiling is the sandbox boundary rather than the host. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms a network-delivered, unauthenticated attack that depends on the victim rendering attacker-controlled content, with high confidentiality and integrity impact inside the affected component and no scope change to the OS. Affected builds map to Google Chrome desktop prior to 156.0.8078.47, as recorded in the EUVD affected-version data and the October 2026 stable channel release notes.
Know when Chromium 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 with no auth (AV:N/PR:N) but requires the victim to visit it (UI:R); sandbox containment keeps scope Unchanged with full renderer-level C/I/A impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in XML 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 desktop installations older than 156.0.8078.47 contain a high-severity memory-corruption defect in XML processing that could allow a remote attacker to execute code within the browser's renderer sandbox when a user opens a crafted HTML page. Because Chrome is widely deployed across the workforce, unpatched endpoints create a broad exposure surface, although the sandbox and required user interaction limit the attack path. No public exploit or confirmed active exploitation was identified, and Google has released a fixed build.
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.
Remote code execution in Google Chrome's ANGLE graphics layer allows attackers to compromise systems via crafted HTML pa
Use-after-free in the Workers component of Google Chrome allows an unauthenticated remote attacker to execute arbitrary
Use-after-free in Google Chrome's WebAppInstalls component allows a remote, unauthenticated attacker to execute arbitrar
Remote code execution inside the renderer sandbox can be triggered in unpatched Google Chrome builds by a use-after-free
Use-after-free in the Canvas rendering path of Google Chrome versions prior to 155.0.8059.79 allows a remote attacker to
Use-after-free in Chrome's V8 JavaScript engine allows remote, unauthenticated attackers to execute arbitrary code insid
Use after free in ANGLE in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap c
The Fonts implementation in Google Chrome before 40.0.2214.91 does not initialize memory for a data structure, which all
Multiple unspecified vulnerabilities in Google Chrome before 40.0.2214.91 allow attackers to cause a denial of service o
Multiple unspecified vulnerabilities in Google V8 before 3.30.33.15, as used in Google Chrome before 40.0.2214.91, allow
The SelectionOwner::ProcessTarget function in ui/base/x/selection_owner.cc in the UI implementation in Google Chrome bef
Skia, as used in Google Chrome before 40.0.2214.91, allows remote attackers to cause a denial of service (out-of-bounds
Exploit-DB