Skip to content

Cube Core is vulnerable to privilege escalation via a specially crafted request

High severity GitHub Reviewed Published Feb 9, 2026 in cube-js/cube • Updated Feb 10, 2026

Package

npm @cubejs-backend/server-core (npm)

Affected versions

>= 0.27.19, < 1.0.14
>= 1.1.0, < 1.4.2
>= 1.5.0, < 1.5.13

Patched versions

1.0.14
1.4.2
1.5.13

Description

Impact

It is possible to make a specially crafted request with a valid API token that leads to privilege escalation.

Affected Versions:

≥= 0.27.19

Mitigation:

Upgrade to a patched version:

  • 1.5.13 and later (regular release)
  • 1.4.2 (active LTS release)
  • 1.0.14 (end-of-life LTS release)

References

The issue was reported by our Core engineer, Dmitrii Patsura (@ovr), in our internal Slack and was promptly patched in a recent update.

References

@bsod90 bsod90 published to cube-js/cube Feb 9, 2026
Published by the National Vulnerability Database Feb 9, 2026
Published to the GitHub Advisory Database Feb 10, 2026
Reviewed Feb 10, 2026
Last updated Feb 10, 2026

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(6th percentile)

Weaknesses

Reliance on Untrusted Inputs in a Security Decision

The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. Learn more on MITRE.

CVE ID

CVE-2026-25958

GHSA ID

GHSA-v226-32c7-x2v7

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.