CVE-2026-64868 New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
Unauthenticated attackers can cause denial of service via memory or disk exhaustion by sending large payloads to payment webhooks before signature validation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-64868?
CVE-2026-64868 is a high-severity denial of service vulnerability in QuantumNous new-api, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-64868?
3 open source packages ship an affected version, including github.com/QuantumNous/new-api.
| Package | Affected | Fixed in |
|---|---|---|
github.com/QuantumNous/new-api Go | All versions | 1.0.0-rc.11 |
github.com/QuantumNous/new-api Go | All versions | 1.0.0-rc.11 |
github.com/QuantumNous/new-api Go | All versions | 1.0.0-rc.11 |
How do I fix CVE-2026-64868?
Upgrade github.com/QuantumNous/new-api to 1.0.0-rc.11 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-64868 being exploited?
There is no known exploitation of CVE-2026-64868 in the wild and no public exploit code.
Sources
Also known as GHSA-v828-m3pf-vq9q, GO-2026-6245.