Vega Cross-Site Scripting (XSS) via expressions abusing toString calls in environments using the VEGA_DEBUG global variable

Summary

Vega is a visualization grammar, a declarative format for creating, saving, and sharing interactive visualization designs. In Vega prior to version 6.2.0, applications meeting 2 conditions are at risk of arbitrary JavaScript code execution, even if "safe mode" expressionInterpreter is used. They are vulnerable if they use `vega` in an application that attaches `vega` library and a `vega.View` instance similar to the Vega Editor to the global `window` and if they allow user-defined Vega `JSON` definitions (vs JSON that was is only provided through source code). Patches are available in the following Vega applications. If using the latest Vega line (6.x), upgrade to `vega` `6.2.0` / `vega-expression` `6.1.0` / `vega-interpreter` `2.2.1` (if using AST evaluator mode). If using Vega in a non-ESM environment, upgrade to `vega-expression` `5.2.1` / `1.2.1` (if using AST evaluator mode). Some workarounds are available. Do not attach `vega` View instances to global variables, and do not attach `vega` to the global window. These practices of attaching the vega library and View instances may be convenient for debugging, but should not be used in production or in any situation where vega/vega-lite definitions could be provided by untrusted parties.

Timeline

1. Nov 13, 2025, 7:54 PM UTCCVE published
2. Nov 14, 2025, 3:59 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Nov 14, 2025, 4:00 PM UTCRecord last updated

Affected versions

• vega vega

  vega < 6.2.0, vega-expression < 5.2.1, vega-interpreter < 1.2.1

• veganpm

  fixed in 6.2.0

• vega-expressionnpm

  From 6.0.0 · fixed in 6.1.0

• vega-interpreternpm

  From 2.0.0 · fixed in 2.2.1

• vega-interpreternpm

  fixed in 1.2.1

• vega-expressionnpm

  fixed in 5.2.1

References 1