CVE-2026-25958
HIGHCVE-2026-25958 is a high-severity (CVSS 7.7) CWE-807 vulnerability in @cubejs-backend/server-core. O3 Security confirms whether CVE-2026-25958 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cube privilege escalation via a specially crafted request
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@cubejs-backend/server-corenpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @cubejs-backend/server-core | ≥ 0.27.19&&< 1.0.14 | 1.0.14 |
| 📦npm | @cubejs-backend/server-core | ≥ 1.1.0&&< 1.4.2 | 1.4.2 |
| 📦npm | @cubejs-backend/server-core | ≥ 1.5.0&&< 1.5.13 | 1.5.13 |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 CVE-2026-25958 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-25958 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-25958. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-25958 in your dependencies?
O3 detects CVE-2026-25958 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.