CVE-2026-25958
Privilege Escalation in Cube Semantic Layer via Crafted API Request
Publication date: 2026-02-09
Last updated on: 2026-02-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| cube | cube.js | From 0.27.19 (inc) to 1.0.14 (exc) |
| cube | cube.js | From 1.1.0 (inc) to 1.4.2 (exc) |
| cube | cube.js | From 1.5.0 (inc) to 1.5.13 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-807 | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Cube, a semantic layer for building data applications. In versions from 0.27.19 up to but not including 1.5.13, 1.4.2, and 1.0.14, an attacker with a valid API token can craft a special request that leads to privilege escalation.
How can this vulnerability impact me? :
The vulnerability allows an attacker with a valid API token to escalate their privileges, potentially gaining higher access rights than intended. This can lead to unauthorized access to sensitive data or system functions.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Cube to one of the fixed versions: 1.5.13, 1.4.2, or 1.0.14.