Vulnerability · Published Jan 5, 2026 · Assigned by GitHub_M
CVE-2025-65110Vega Cross-Site Scripting (XSS) via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope
High 8.1
In plain English
A high-severity cross-site scripting in vega from vega. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 43% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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 `vega-selections@6.1.2` (requires ESM) for Vega v6 and `vega-selections@5.6.3` (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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | vega.js | no fix listed | DEBIAN-CVE-2025-65110 |
| Debian:13 | vega.js | no fix listed | DEBIAN-CVE-2025-65110 |
| Debian:14 | vega.js | 5.33.1+ds+~cs5.3.0-4 | DEBIAN-CVE-2025-65110 |
| Ubuntu:24.04:LTS | vega.js | no fix listed | UBUNTU-CVE-2025-65110 |
| Ubuntu:25.10 | vega.js | no fix listed | UBUNTU-CVE-2025-65110 |
| Ubuntu:26.04:LTS | vega.js | no fix listed | UBUNTU-CVE-2025-65110 |
| Ubuntu:26.10 | vega.js | no fix listed | UBUNTU-CVE-2025-65110 |
| npm | vega-selections | 6.1.2 | GHSA-829q-m3qg-ph8r |
| npm | vega-selections | 5.6.3 | GHSA-829q-m3qg-ph8r |
Affected products (as reported)
Weakness: CWE-79 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
References
- https://github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8r x_refsource_CONFIRM