CVE-2025-65110 Details
Description
Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. Prior to versions 6.1.2 and 5.6.3, applications meeting two conditions are at risk of arbitrary JavaScript code execution, even if "safe mode" expressionInterpreter is used. First, they use `vega` in an application that attaches both `vega` library and a `vega.View` instance similar to the Vega Editor to the global `window`, or has any other satisfactory function gadgets in the global scope. Second, they allow user-defined Vega `JSON` definitions (vs JSON that was is only provided through source code). This vulnerability allows for DOM XSS, potentially stored, potentially reflected, depending on how the library is being used. The vulnerability requires user interaction with the page to trigger. An attacker can exploit this issue by tricking a user into opening a malicious Vega specification. Successful exploitation allows the attacker to execute arbitrary JavaScript in the context of the application’s domain. This can lead to theft of sensitive information such as authentication tokens, manipulation of data displayed to the user, or execution of unauthorized actions on behalf of the victim. This exploit compromises confidentiality and integrity of impacted applications.Patched versions are available in `[email protected]` (requires ESM) for Vega v6 and `[email protected]` (no ESM needed) for Vega v5. As a workaround, do not attach `vega` or `vega.View` instances to global variables or the window as the editor used to do. This is a development-only debugging practice that should not be used in any situation where Vega/Vega-lite definitions can come from untrusted parties.
A vulnerability in Vega prior to versions 6.1.2 and 5.6.3 allows arbitrary JavaScript code execution, leading to DOM-based cross-site scripting (XSS). This issue arises when applications use the Vega library in a way that exposes function gadgets to the global scope and permit user-defined Vega JSON definitions. The vulnerability can be exploited even with the 'safe mode' expression interpreter active, by tricking users into opening malicious Vega specifications. Successful exploitation enables attackers to execute arbitrary JavaScript in the context of the application's domain, potentially leading to the theft of sensitive information, manipulation of displayed data, or execution of unauthorized actions on behalf of the user.
Users can update to '[email protected]' for Vega v6 or '[email protected]' for Vega v5. As a workaround, avoid attaching Vega or 'vega.View' instances to global variables or the window.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jan 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8r | CISA-ADP | ExploitVendor Advisory |
| https://github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8r | [email protected] | ExploitVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-79 | Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| vega project vega | < 5.6.3 >= 6.0.0, < 6.1.2 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jan 30, 2026 | Initial Analysis | [email protected] |
| Jan 5, 2026 | New CVE Received | [email protected] |
| Jan 5, 2026 | CVE Modified | CISA-ADP |