Skip to main content
VulnerabilityPublished

CVE-2025-59840: vega · Cross-site Scripting

Affects vegaSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 6.1.0 or 2.2.1 soon.

Data as of 13 Nov 2026, 18:46 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.1
Patch
Available – fixed in 6.1.0, 2.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade vega to 6.1.0 or 2.2.1.

Affected software

ProductAffectedFixed in
vega vegaAffected
  • <6.1.0
  • <2.2.1
Fixed in
  • 6.1.0
  • 2.2.1

AI-suggested

Apply the official patches by upgrading to Vega 6.2.0 or later, vega-expression 6.1.0 or later, and vega-interpreter 2.2.1 or later if using AST evaluator mode. For non-ESM environments, upgrade to vega-expression 5.2.1 or 1.2.1 accordingly. If patching is not immediately possible, do not attach Vega or Vega.View instances to global variables or the global window object, and avoid accepting Vega JSON definitions from untrusted sources. These workarounds reduce the risk of exploitation.

Description

CVE-2025-59840 is a high-severity cross-site scripting (XSS) vulnerability in the Vega visualization grammar prior to version 6.2.0. The flaw allows arbitrary JavaScript code execution when applications attach the Vega library and a Vega.View instance to the global window object and accept user-defined Vega JSON definitions. This risk exists even if the 'safe mode' expressionInterpreter is used. Patches are available in Vega 6.2.0 and related component updates. Workarounds include avoiding attaching Vega instances to global variables and not exposing Vega to untrusted JSON inputs.

References

Community reviews

Loading reviews…