cube-js cube up to 1.4.1/1.5.12 Cube API Endpoint exceptional condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic was found in cube-js cube up to 1.4.1/1.5.12. Affected is an unknown function of the component Cube API Endpoint. Executing a manipulation can lead to exceptional condition. This vulnerability appears as CVE-2026-25957. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in cube-js cube up to 1.4.1/1.5.12. It has been declared as problematic. This vulnerability affects an unknown function of the component Cube API Endpoint. The manipulation with an unknown input leads to a exceptional condition vulnerability. The CWE definition for the vulnerability is CWE-755. The product does not handle or incorrectly handles an exceptional condition. As an impact it is known to affect availability. CVE summarizes:

Cube is a semantic layer for building data applications. From 1.1.17 to before 1.5.13 and 1.4.2, it is possible to make the entire Cube API unavailable by submitting a specially crafted request to a Cube API endpoint. This vulnerability is fixed in 1.5.13 and 1.4.2.

The advisory is available at github.com. This vulnerability was named CVE-2026-25957 since 02/09/2026. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available.

Upgrading to version 1.4.2 or 1.5.13 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

Name

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA Base Score: 6.5
CNA Vector (GitHub_M): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Exceptional condition
CWE: CWE-755
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: cube 1.4.2/1.5.13

Timelineinfo

02/09/2026 CVE reserved
02/10/2026 +1 days Advisory disclosed
02/10/2026 +0 days VulDB entry created
02/26/2026 +16 days VulDB entry last update

Sourcesinfo

Product: github.com

Advisory: GHSA-9vph-2hvm-x66g
Status: Confirmed

CVE: CVE-2026-25957 (🔒)
GCVE (CVE): GCVE-0-2026-25957
GCVE (VulDB): GCVE-100-345058

Entryinfo

Created: 02/10/2026 03:16
Updated: 02/26/2026 14:36
Changes: 02/10/2026 03:16 (64), 02/26/2026 14:36 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!