CVE-2026-25958CWE-807

Cube privilege escalation via a specially crafted request

High · published February 9, 2026

CVSS v3.1
7.7
EPSS
0%
Percentile
37.3
In the wild
Unconfirmed
What it is

⚡ A crafty request using a valid API token could let attackers rise to the top! This privilege escalation flaw in Cube is like a sneaky employee getting a promotion without the necessary qualifications! Think of it like a restaurant where a diner with a reservation can suddenly walk into the kitchen and start cooking — it disrupts the entire system! A specially crafted request can gain access to areas that should be off-limits, compromising the integrity of your data applications. An attacker could exploit this vulnerability to gain elevated privileges, allowing them to access sensitive data or manipulate application behavior. This could lead to unauthorized actions that jeopardize the security and reliability of your data applications, making it absolutely devastating for your organization!

Put simply

Think of it like a restaurant where a diner with a reservation can suddenly walk into the kitchen and start cooking — it disrupts the entire system! A specially crafted request can gain access to areas that should be off-limits, compromising the integrity of your data applications. The privilege escalation vulnerability arises from improperly validated requests that allow authenticated users to access functionalities intended for higher privilege roles. From version 0.27.19 up to before 1.5.13, 1.4.2, and 1.0.14, this flaw could be exploited via specially crafted requests using a valid API token.

What to do

An attacker could exploit this vulnerability to gain elevated privileges, allowing them to access sensitive data or manipulate application behavior. This could lead to unauthorized actions that jeopardize the security and reliability of your data applications, making it absolutely devastating for your organization! Upgrade your Cube installation to version 1.5.13, 1.4.2, or 1.0.14 immediately to close this vulnerability. Ensure all API tokens are managed securely and review permissions regularly to prevent unauthorized access. You've got this! Following these steps will help you secure your data applications and maintain your security hero status! 🛡️

The record
Technical detail
CVSS v3.1
7.7 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
CVSS v4.0
Not supplied
EPSS
0.00441 · 37.3th percentile
Weakness
CWE-807 · Reliance on Untrusted Inputs in a Security Decision
Published
2026-02-09T22:42Z
EPSS history
Timeline
  • 09 FEB 22:42Z
    Cube privilege escalation via a specially crafted request
    cvelistv5