Skip to main content
VulnerabilityPublished

CVE-2026-64868: QuantumNous new-api · Uncontrolled Resource Consumption

Affects QuantumNous new-apiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.0.0-rc.11 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.0-rc.11
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade QuantumNous new-api to 1.0.0-rc.11.

Affected software

ProductAffectedFixed in
QuantumNousnew-apiAffected
  • <1.0.0-rc.11
Fixed in
  • 1.0.0-rc.11
GitHubquantumnous/new-apipkg:github/quantumnous/new-apiOther threatsAffected
  • =1.0.0-rc.11
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade QuantumNous new-api to version 1.0.0-rc.11 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor's advisory stating the fix in 1.0.0-rc.11. No other mitigations are indicated.

Description

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.11, POST /api/stripe/webhook, POST /api/creem/webhook, and POST /api/waffo/webhook read and log full request bodies before signature validation in router/api-router.go and the payment controllers, allowing an unauthenticated attacker to cause memory pressure, container restarts, or disk exhaustion without forging a successful payment. This issue is fixed in version 1.0.0-rc.11.

References

Community reviews

Loading reviews…