Skip to content
Fencer Intel
high 7.7

CVE-2026-25958 json

Cube privilege escalation via a specially crafted request

published 9mo ago modified 4mo ago also EUVD-2026-6241 , GHSA-v226-32c7-x2v7

cvss
7.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 32%
public exploits
0
none known

Summary

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 in 1.5.13, 1.4.2, and 1.0.14.

Patch / fix

  • npm @cubejs-backend/server-core 1.0.14, 1.4.2, 1.5.13
  • cube cube.js 1.0.14, 1.4.2, 1.5.13

Is CVE-2026-25958 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
8mo ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 7.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm @cubejs-backend/server-core
>=0.27.19, <1.0.14
>=1.1.0, <1.4.2
>=1.5.0, <1.5.13
1.0.14
1.4.2
1.5.13

Affected products

  • cube-js cube

Classification

Weakness
  • CWE-807 Reliance on Untrusted Inputs in a Security Decision

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.