@cubejs-backend/api-gateway row level security bypassGHSA-6jqm-3c9g-pch7
HIGHFix: cube-js/cube.js@3c61467GHSA-6jqm-3c9g-pch7 is a high-severity (CVSS 7.7) SQL Injection vulnerability in @cubejs-backend/api-gateway. A fix is available for @cubejs-backend/api-gateway — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6jqm-3c9g-pch7.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@cubejs-backend/api-gatewaynpmDescription
Impact
All authenticated Cube clients could bypass row-level security and run arbitrary SQL via the newly introduced /v1/sql-runner endpoint.
Patches
The change has been reverted in 0.31.24
Workarounds
Upgrade to >=0.31.24 or downgrade to <=0.31.22
Post mortem
As part of implementing the Cube Cloud SQL runner functionality, we’ve added a new endpoint to the Cube Core so that we could add arbitrary queries directly to the queue, bypassing the modeling layer.
The endpoint was added in this commit: https://github.com/cube-js/cube.js/commit/f1e25bb50323c0b99f3891d349467e7b637baeea
It went through the code review; however, it slipped everyone’s attention that this endpoint completely bypasses any row-level security logic implemented in the modeling layer. Now anyone with a valid Cube JWT token could fetch any data, even if they were not allowed to do so by their security context.
The issue was noticed by the Core team on Dec 12 and immediately reverted.
The just-released 0.31.23 version of the Cube has been pulled out of all the registries, and a CVE was published on Github. Another change (https://github.com/cube-js/cube.js/commit/2c5db32f2ded074ebe5e83668eee8c024101240b) was also rolled back along with the SQL runner endpoint. It didn't pose a significant security threat, but it increased the attacker’s ability to enumerate cube schema, and it should be revisited.
The 0.31.24 was released to replace the revoked version with a change completely reverted. All customers are urged to upgrade to the newest Cube version.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @cubejs-backend/api-gateway | ≥ 0.31.23&&< 0.31.24 | 0.31.24npm install @cubejs-backend/api-gateway@0.31.24 |
Affected Products
cube.jscubeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @cubejs-backend/api-gateway, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @cubejs-backend/api-gateway to 0.31.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6jqm-3c9g-pch7 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is GHSA-6jqm-3c9g-pch7 in your dependencies?
Find it across npm, including transitive dependencies.