Cube Core is vulnerable to privilege escalation via a specially crafted requestGHSA-v226-32c7-x2v7
HIGHGHSA-v226-32c7-x2v7 is a high-severity (CVSS 7.7) CWE-807 vulnerability in @cubejs-backend/server-core. A fix is available for @cubejs-backend/server-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- 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-v226-32c7-x2v7.
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/server-corenpmDescription
Impact
It is possible to make a specially crafted request with a valid API token that leads to privilege escalation.
Affected Versions:
≥= 0.27.19
Mitigation:
Upgrade to a patched version:
- 1.5.13 and later (regular release)
- 1.4.2 (active LTS release)
- 1.0.14 (end-of-life LTS release)
References
The issue was reported by our Core engineer, Dmitrii Patsura (@ovr), in our internal Slack and was promptly patched in a recent update.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @cubejs-backend/server-core | ≥ 0.27.19&&< 1.0.14 | 1.0.14npm install @cubejs-backend/server-core@1.0.14 |
| 📦npm | @cubejs-backend/server-core | ≥ 1.1.0&&< 1.4.2 | 1.4.2npm install @cubejs-backend/server-core@1.4.2 |
| 📦npm | @cubejs-backend/server-core | ≥ 1.5.0&&< 1.5.13 | 1.5.13npm install @cubejs-backend/server-core@1.5.13 |
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/server-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @cubejs-backend/server-core to 1.0.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v226-32c7-x2v7 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-v226-32c7-x2v7 in your dependencies?
Find it across npm, including transitive dependencies.