GHSA-4j6x-w426-6rc6 — @cubejs-backend/api-gatew…
GHSA-4j6x-w426-6rc6 is a security vulnerability in @cubejs-backend/api-gateway. A fix is available for @cubejs-backend/api-gateway — see the affected versions and patch details below.
Default Express middleware security check is ignored in production
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
Default Express middleware security check is ignored in production
Impact
All Cube.js deployments that use affected versions of @cubejs-backend/api-gateway with default express authentication middleware in production environment are affected.
Patches
@cubejs-backend/[email protected]
Workarounds
Override default authentication express middleware: https://cube.dev/docs/@cubejs-backend-server-core#options-reference-check-auth-middleware
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/cube-js/cube.js/issues
- Reach out us in community Slack: https://slack.cube.dev/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @cubejs-backend/api-gateway | ≥ 0.11.0&&< 0.11.17 | 0.11.17npm install @cubejs-backend/api-gateway@0.11.17 |
Detection & 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.11.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4j6x-w426-6rc6 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4j6x-w426-6rc6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4j6x-w426-6rc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4j6x-w426-6rc6 in your dependencies?
O3 Security finds GHSA-4j6x-w426-6rc6 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.