INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-64868

New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging

CVE-2026-64868 ยท 2026-08-17 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Denial of service
Affected
github.com/QuantumNous/new-api (Go)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% chance of exploitation in 30 days

How it works, in short

Unauthenticated payment webhook routes read and log entire request bodies before signature checks, so oversized requests exhaust memory and disk. (Our summary, written by a model. The source text is below.)

Details

Summary

Unauthenticated payment webhook endpoints could read and log the entire request body before validating the webhook signature. When a payment webhook was enabled, an unauthenticated attacker could send oversized requests to public callback endpoints and force excessive memory use and log growth before the request was rejected.

Affected public endpoints included:

This issue did not allow forging successful payments, because signature validation still guarded the payment processing logic. The vulnerable behavior was the expensive unauthenticated request processing that occurred before signature validation.

Impact

A remote unauthenticated attacker could cause denial of service through memory pressure, container OOM/restarts, or disk consumption from full-body logging. The impact is availability-only and is rated High.

Affected versions

Versions before v1.0.0-rc.11 are affected. The earlier affected range of <= v1.0.0-rc.7 was incomplete; the anonymous request body limit was introduced later and first appears in v1.0.0-rc.11.

Patches

This issue is fixed in v1.0.0-rc.11. The fix adds middleware.AnonymousRequestBodyLimit() and applies it to unauthenticated POST routes, including the payment webhook callbacks. The default limit is controlled by ANONYMOUS_REQUEST_BODY_LIMIT_KB and defaults to 512 KiB.

Workarounds

If upgrading immediately is not possible, operators should disable unused payment webhooks, enforce request body limits at a reverse proxy or load balancer, and ensure application and container logs have rotation and quotas. These mitigations reduce exposure but do not replace upgrading.

References

References

Source: GitHub Advisory Database, used under CC BY 4.0.