CVE-2025-65110: vega_project vega Cross-site Scripting
Vulnerability summary
CVE-2025-65110 is a critical (CVSS 9.3) Cross-site Scripting vulnerability in vega_project vega. EPSS estimates a 0.50% chance of exploitation in the next 30 days, higher than 42.1% of scored vulnerabilities. 1 public exploit is recorded.
Timeline
- 05-01-2026PublishedVulnerability first disclosed.
- 05-01-2026Last modifiedVulnerability information updated.
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.
CVSS metrics
5 scores · 5 sources · 1 version- CVE.orgCNA8.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NDiffers
- OSV · UbuntuEcosystem advisory · calculated9.3CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- OSV · DebianEcosystem advisory · calculated9.3CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N
- OSV · NpmEcosystem advisory · calculated8.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NDiffers
EPSS trend
Probability
0.50%
Chance of exploitation in the next 30 days
Percentile
42%
Versus all other CVEs
30-day change
-0.01 pp
From 0.52% on 21-09-2026
Known exploited
Compare KEV catalogsNot in any of the 3 tracked catalogs.
Public exploits
1 foundVega
Maturity: poc
Weaknesses
CWE · root causeAffected systems
Debian1 product
- vega.jsAll versions (No fix recorded) | < 5.33.1+ds+~cs5.3.0-4
Npm1 product
- vega-selections< 5.6.3 | ≥ 6.0.0, < 6.1.2
Ubuntu1 product
- vega.jsAll versions (No fix recorded)
Vega1 product
- vega< 5.6.3 | ≥ 6.0.0, < 6.1.2
Vega_project1 product
- vega< 5.6.3 | ≥ 6.0.0, < 6.1.2
5 vendors · 5 products
References
6 links- github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8rX Refsource CONFIRMREPORTWEBExploitVendor Advisory
- github.com/vega/vegaPACKAGE