What is the CVSS score of CVE-2026-25958?

CVE-2026-25958 has a CVSS 3.1 base score of 7.7 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2026-25958?

Within 24 hours: Inventory all Cube deployments and identify affected versions; restrict API token distribution and rotate existing tokens immediately. Within 7 days: Implement network segmentation to limit Cube access, enable comprehensive API logging and monitoring for suspicious token usage patterns, and escalate to vendor for patch timeline. Within 30 days: Upgrade to patched versions (1.5.13, 1.4.2, or 1.0.14 or later) as soon as available, conduct access review audit, and implement principle of least privilege for all API token assignments.

Cube CVE-2026-25958

HIGH

Reliance on Untrusted Inputs in a Security Decision (CWE-807)

2026-02-09 security-advisories@github.com

GHSA-v226-32c7-x2v7

Privilege Escalation Cube.Js Cube Cube Js

7.7

CVSS 3.1 · GitHub Advisory

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Obtain valid API token
Exploit

Craft malicious request with token
Execution

Bypass authorization checks
Impact

Escalate privileges to higher role

Vulnerability Assessment

Weakness	CWE CWE-807 OWASP Top 10:2025 A06:2025 - Insecure Design ASVS 5.0 V2 - Validation and Business Logic Trusted input validation
Exploitation Conditions	Valid API token required; vulnerable Cube versions 0.27.19 to before 1.5.13, 1.4.2, and 1.0.14; authenticated user account necessary for token possession.
Impact	CVSS 7.7 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: Low. User interaction: None.
Exploit ScenarioDerived	An attacker could exploit this flaw, privilege escalation.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Privilege escalation in Cube.js versions 0.27.19 through 1.5.12 allows authenticated attackers to craft specially designed API requests that bypass access controls and gain elevated privileges within the application. This vulnerability affects Cube.js semantic layer deployments and requires only a valid API token to exploit, making it a risk to multi-tenant or role-based access control implementations. No patch is currently available for this HIGH severity issue.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 7.7

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. [CVSS 7.7 HIGH]

RemediationAI

Fixed in version 1.5.13. Restrict network access to the affected service where possible.

Affected Packages

npm @cubejs-backend/server-core fix: 1.0.14, 1.4.2, 1.5.13

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Affects Cube.Js. 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.

Know when Cube gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 7.7 HIGH

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

CVE Published

Feb 09, 2026 - 23:16 nvd

HIGH 7.7

DescriptionGitHub Advisory

Executive ViewAI

Why It Matters

Cube semantic layer deployments are vulnerable to privilege escalation attacks when users possess valid API tokens, potentially allowing attackers to gain unauthorized administrative access to data applications and underlying data assets. Organizations using affected Cube versions (0.27.19 through 1.5.12, 1.4.1, and 1.0.13) face immediate risk of data exposure and unauthorized data manipulation without a vendor patch currently available.

Business Impact: High

Compensating Controls

Implement API gateway WAF rules to detect and block malformed or suspicious Cube API requests; enforce strict network segmentation restricting Cube access to authorized subnets only; disable public internet exposure of Cube instances; implement robust API token monitoring and alerting for anomalous authentication patterns; rotate all API tokens immediately and enforce shorter token expiration windows; implement database-level access controls to limit damage from compromised Cube instances; enable comprehensive audit logging of all data access through Cube.

Threat Intelligence Overview

EPSS Score

0.0%

Top 96% exploitable

Data Quality

4 sources

Confidence: Medium

NVD

CVE.org

EPSS

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived

Scheduled

Exploitation· derived

None

System Exposure· derived

Open

Automatable· derived

Human Impact

High

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Privilege Escalation HIGH

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.