UBUNTU-CVE-2025-65110 (CVE-2025-65110)
Vulnerability from osv_ubuntu – Published: 2026-01-05 22:15 – Updated: 2026-10-17 09:36 – Source websiteVega 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": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-vega",
"binary_version": "5.25.0+ds+~cs5.3.0-5"
},
{
"binary_name": "node-vega",
"binary_version": "5.25.0+ds+~cs5.3.0-5"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "vega.js",
"purl": "pkg:deb/ubuntu/vega.js@5.25.0+ds+~cs5.3.0-5?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.25.0+ds+~cs5.3.0-2",
"5.25.0+ds+~cs5.3.0-5"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-vega",
"binary_version": "5.28.0+ds+~cs5.3.0-1"
},
{
"binary_name": "node-vega",
"binary_version": "5.28.0+ds+~cs5.3.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "vega.js",
"purl": "pkg:deb/ubuntu/vega.js@5.28.0+ds+~cs5.3.0-1?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.28.0+ds+~cs5.3.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-vega",
"binary_version": "5.33.1+ds+~cs5.3.0-4"
},
{
"binary_name": "node-vega",
"binary_version": "5.33.1+ds+~cs5.3.0-4"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.10",
"name": "vega.js",
"purl": "pkg:deb/ubuntu/vega.js@5.33.1+ds+~cs5.3.0-4?arch=source\u0026distro=stonking"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.28.0+ds+~cs5.3.0-2",
"5.33.1+ds+~cs5.3.0-4"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "libjs-vega",
"binary_version": "5.28.0+ds+~cs5.3.0-2"
},
{
"binary_name": "node-vega",
"binary_version": "5.28.0+ds+~cs5.3.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "vega.js",
"purl": "pkg:deb/ubuntu/vega.js@5.28.0+ds+~cs5.3.0-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"5.28.0+ds+~cs5.3.0-1",
"5.28.0+ds+~cs5.3.0-2"
]
}
],
"aliases": [],
"details": "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\u2019s 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.",
"id": "UBUNTU-CVE-2025-65110",
"modified": "2026-10-17T09:36:24Z",
"published": "2026-01-05T22:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2025-65110"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-65110"
},
{
"type": "REPORT",
"url": "https://github.com/vega/vega/security/advisories/GHSA-829q-m3qg-ph8r"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2025-65110"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.