VulnerabilityPublished 9 Feb 2026Updated 11 Feb 2026

CVE-2026-25958: cube · Reliance on Untrusted Inputs in a Security Decision

Affects cubeSource CVE Database V5

Not known to be exploited · CVSS 7.7 High · fixed in 1.5.13 : patch cube soon.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.5.13, 1.4.2, 1.0.14

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade cube to 1.5.13, 1.4.2 or 1.0.14.

Affected software

Product	Affected	Fixed in
cube-jscube	Affected >=1.5.0 <1.5.13	Fixed in 1.5.13
cube-jscube	Affected >=1.1.0 <1.4.2	Fixed in 1.4.2
cube-jscube	Affected >=0.27.19 <1.0.14	Fixed in 1.0.14

AI-suggested

Immediate upgrade of cube-js to patched versions 1.5.13, 1.4.2, or 1.0.14 depending on the deployment version.
Restrict API token issuance and enforce strict token scope and expiration policies to minimize the risk of token misuse.
Implement network-level access controls to limit exposure of cube-js endpoints to trusted internal networks or VPNs.
Monitor API usage logs for unusual or anomalous requests that could indicate exploitation attempts.
Employ runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block suspicious request patterns targeting privilege escalation.
Conduct regular security audits and penetration testing focusing on authentication and authorization mechanisms within cube-js deployments.
Educate developers and administrators on secure coding and configuration practices to prevent reliance on untrusted inputs in security decisions.
Apply the principle of least privilege in API token generation and user roles to limit potential damage from compromised tokens.

Description

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.

Impact

For European organizations, the impact of CVE-2026-25958 can be substantial, especially those relying on cube-js for data analytics, business intelligence, or other data application layers. Privilege escalation can lead to unauthorized access to sensitive business data, violating confidentiality and potentially breaching GDPR requirements. This could result in regulatory penalties, reputational damage, and loss of customer trust. Since the vulnerability does not affect integrity or availability directly, the primary concern is unauthorized data exposure. Attackers with limited access could leverage this flaw to escalate privileges and access broader datasets or administrative functions. Organizations in sectors such as finance, healthcare, and government, where data sensitivity is paramount, are particularly at risk. The remote exploitability and lack of user interaction required increase the likelihood of exploitation if the vulnerability remains unpatched.

CWE-807Reliance on Untrusted Inputs in a Security Decision (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
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.
Architecture and Design · Attack Surface Reduction
Store state information and sensitive data on the server side only.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/cube-js/cube/security/advisories/GHSA-v226-32c7-x2v7 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Feb 2026, 09:18 UTC

WeaknessesCWE-807

Technical details

References

Community reviews

Related threats