CVE-2026-25958
Cube.Js 0.27.19 – 1.0.14
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25958 is a high-severity Reliance on Untrusted Inputs in a Security Decision (CWE-807) vulnerability in Cube Cube.Js. Its CVSS base score is 7.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25958 is a privilege escalation vulnerability in Cube, a semantic layer for building data applications. It affects versions from 0.27.19 up to but excluding 1.5.13, 1.4.2, and 1.0.14, where a specially crafted request using a valid API token can be made to escalate privileges. The issue carries a CVSS v3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) and is categorized under CWE-807.
An authenticated attacker with low privileges (PR:L), such as one holding a valid API token, can exploit this vulnerability remotely over the network with low attack complexity and no user interaction required. Exploitation changes scope and results in high confidentiality impact, enabling the attacker to escalate privileges and access sensitive data that would otherwise be restricted.
Cube has addressed this vulnerability in versions 1.5.13, 1.4.2, and 1.0.14. Additional details on the issue and remediation are available in the GitHub security advisory at https://github.com/cube-js/cube/security/advisories/GHSA-v226-32c7-x2v7.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-6241
Vulnerability Data
Cube is a semantic layer for building data applications. From 0.27.19 to before 1.5.13, 1.4.2, and 1.0.14, it is possible to make a specially crafted request with a valid API token that leads to privilege escalation. This vulnerability is fixed…
more
in 1.5.13, 1.4.2, and 1.0.14.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.
Input validation can reject malformed or attacker-controlled values before they reach a security decision point.
Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.
Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.
Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.
Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.
Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.
Security testing in development catches input-validation flaws before deployment.
Monitoring can detect exploitation but does not stop the underlying weakness.
Application security requirements explicitly call for validation of inputs used in security decisions.
Secure architecture principles mandate treating all external inputs as untrusted.
Access-control rules can be bypassed if they rely on untrusted inputs.