Cube API denial of service attack

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-50709: 0.72% estimated exploitation activity in the next 30 days; percentile 54.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact It is possible to make the entire Cube API unavailable by submitting a specially crafted request to a Cube API endpoint. Patches The issue has been patched in the v0.34.34 and it's recommended that all users exposing Cube APIs to the public internet upgrade to the latest version to prevent service disruption. Workarounds There are currently no workaround for older versions, and the recommendation is to upgrade. References The issue was reported by y0d3n in our Community Slack and has been promptly patched in the recent update.

Published by the source

13 Dec 2023, 23:15 UTC

Last modified by the source

19 Dec 2023, 20:39 UTC

Source last checked

26 Oct 2026, 12:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-9759-3276-g2pm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-9759-3276-g2pm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-50709

Advisory: Cube API denial of service attack
IDs: CVE-2023-50709, GHSA-9759-3276-g2pm
Record: https://patchnext.com/advisories/cve-2023-50709 (revision 2, source checked 26 Oct 2026, 12:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @cubejs-backend/api-gateway 0.34.34. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @cubejs-backend/api-gateway: affected < 0.34.34; fixed in 0.34.34

## Suggested inspection (read-only)
- `npm ls @cubejs-backend/api-gateway --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @cubejs-backend/api-gateway.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9759-3276-g2pm (OSV record GHSA-9759-3276-g2pm lists affected ranges: npm @cubejs-backend/api-gateway >=0 <0.34.34 (fixed))
- Verified: https://github.com/advisories/GHSA-9759-3276-g2pm (GitHub-reviewed advisory GHSA-9759-3276-g2pm lists affected ranges: npm @cubejs-backend/api-gateway >=0 <0.34.34)

Commands are suggestions: review each one before running it.