UBUNTU-CVE-2025-65110

Source
https://ubuntu.com/security/CVE-2025-65110
Import Source
https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2025/UBUNTU-CVE-2025-65110.json
JSON Data
https://api.osv.dev/v1/vulns/UBUNTU-CVE-2025-65110
Upstream
Published
2026-01-05T22:15:00Z
Modified
2026-02-03T08:33:21.255130Z
Severity
  • 8.1 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N CVSS Calculator
  • 9.3 (Critical) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N CVSS Calculator
  • Ubuntu - medium
Summary
[none]
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’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.

References

Affected packages

Ubuntu:24.04:LTS / vega.js

Package

Name
vega.js
Purl
pkg:deb/ubuntu/vega.js@5.25.0+ds+~cs5.3.0-5?arch=source&distro=noble

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

5.*
5.25.0+ds+~cs5.3.0-2
5.25.0+ds+~cs5.3.0-5

Ecosystem specific

{
    "binaries": [
        {
            "binary_version": "5.25.0+ds+~cs5.3.0-5",
            "binary_name": "libjs-vega"
        },
        {
            "binary_version": "5.25.0+ds+~cs5.3.0-5",
            "binary_name": "node-vega"
        }
    ]
}

Database specific

source
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2025/UBUNTU-CVE-2025-65110.json"

Ubuntu:25.10 / vega.js

Package

Name
vega.js
Purl
pkg:deb/ubuntu/vega.js@5.28.0+ds+~cs5.3.0-1?arch=source&distro=questing

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected

Affected versions

5.*
5.28.0+ds+~cs5.3.0-1

Ecosystem specific

{
    "binaries": [
        {
            "binary_version": "5.28.0+ds+~cs5.3.0-1",
            "binary_name": "libjs-vega"
        },
        {
            "binary_version": "5.28.0+ds+~cs5.3.0-1",
            "binary_name": "node-vega"
        }
    ]
}

Database specific

source
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2025/UBUNTU-CVE-2025-65110.json"