CVE-2026-64868: New API Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-v828-m3pf-vq9q
CVSS 7.5
CWE-400 CWE-770
Published
Advisory Summary

CVE-2026-64868 is a HIGH (CVSS 7.5) denial of service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting New API libraries in the Go ecosystem. The issue involves unauthenticated payment webhooks allow memory and disk dos via unbounded body reads and full-body logging. Remediation is available by upgrading affected packages to version 1.0.0-rc.11.

CVE-2026-64868 at a Glance

CVE Identifier CVE-2026-64868
GHSA Identifier GHSA-v828-m3pf-vq9q
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product New API
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-64868

To remediate this vulnerability, upgrade all affected New API dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/QuantumNous/new-api fixed: 1.0.0-rc.11
Upgrade github.com/QuantumNous/new-api to 1.0.0-rc.11
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/QuantumNous/new-api

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-64868, inspect your project dependencies for New API:

inspect dependencies for github.com/QuantumNous/new-api

Analyze the terminal output to locate any version of New API in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.0.0-rc.11), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In New API, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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: - `POST /api/stripe/webhook` - `POST /api/creem/webhook` - `POST /api/waffo/webhook` 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 - Fixed by commit `d2f7f9ee3adf3ef66798783a60d7bc712451c85c`. - Relevant code paths: `router/api-router.go`, `middleware/request_body_limit.go`, `controller/topup_stripe.go`, `controller/topup_creem.go`, and `controller/topup_waffo.go`.

CVE-2026-64868 Affected New API Versions

1 component(s)
Fixed Versions:
1.0.0-rc.11
Product / Package Ecosystem Affected Versions Fixed Version
github.com/QuantumNous/new-api
Go
< 1.0.0-rc.11
1.0.0-rc.11

References

Frequently Asked Questions

What is CVE-2026-64868?
CVE-2026-64868 is a security vulnerability in New API involving Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging under CWE-400: Uncontrolled Resource Consumption.
Which New API versions are affected?
Affected versions include releases prior to 1.0.0-rc.11 across affected packages: github.com/QuantumNous/new-api.
What version fixes CVE-2026-64868?
Upgrading to 1.0.0-rc.11 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/QuantumNous/new-api affected?
Yes, github.com/QuantumNous/new-api is affected in releases prior to 1.0.0-rc.11. Upgrade your dependency to 1.0.0-rc.11 or later.
What is the CVSS score of CVE-2026-64868?
CVE-2026-64868 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-64868?
CVE-2026-64868 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Go dependencies for CVE-2026-64868?
Run the dependency tree command: 'inspect dependencies for github.com/QuantumNous/new-api'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-v828-m3pf-vq9q",
  "modified" : "2026-08-17T16:35:58Z",
  "published" : "2026-08-17T16:35:58Z",
  "aliases" : [ "CVE-2026-64868" ],
  "summary" : "New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging",
  "details" : "## Summary\n\nUnauthenticated 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.\n\nAffected public endpoints included:\n\n- `POST /api/stripe/webhook`\n- `POST /api/creem/webhook`\n- `POST /api/waffo/webhook`\n\nThis 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.\n\n## Impact\n\nA 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.\n\n## Affected versions\n\nVersions 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`.\n\n## Patches\n\nThis 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.\n\n## Workarounds\n\nIf 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.\n\n## References\n\n- Fixed by commit `d2f7f9ee3adf3ef66798783a60d7bc712451c85c`.\n- Relevant code paths: `router/api-router.go`, `middleware/request_body_limit.go`, `controller/topup_stripe.go`, `controller/topup_creem.go`, and `controller/topup_waffo.go`.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/QuantumNous/new-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.0.0-rc.11"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/QuantumNous/new-api/security/advisories/GHSA-v828-m3pf-vq9q"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/QuantumNous/new-api/pull/5244"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/QuantumNous/new-api/commit/d2f7f9ee3adf3ef66798783a60d7bc712451c85c"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/QuantumNous/new-api"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/QuantumNous/new-api/releases/tag/v1.0.0-rc.11"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400", "CWE-770" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-17T16:35:58Z",
    "nvd_published_at" : null
  }
}