Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

CVE-2026-64868GHSA-v828-m3pf-vq9q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/QuantumNous/new-api 1.0.0-rc.11), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-64868: 0.64% estimated exploitation activity in the next 30 days; percentile 50.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-v828-m3pf-vq9q

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6245

  3. Revision 1 · created ·

    Published from osv record GHSA-v828-m3pf-vq9q

Agent brief

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

# Patch Next advisory brief: CVE-2026-64868

Advisory: New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
IDs: CVE-2026-64868, GHSA-v828-m3pf-vq9q
Record: https://patchnext.com/advisories/cve-2026-64868 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/QuantumNous/new-api 1.0.0-rc.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/QuantumNous/new-api: affected < 1.0.0-rc.11; fixed in 1.0.0-rc.11

## Suggested inspection (read-only)
- Go github.com/QuantumNous/new-api: check the installed version with your package manager.

## 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 github.com/QuantumNous/new-api.
- 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-v828-m3pf-vq9q (OSV record GHSA-v828-m3pf-vq9q lists affected ranges: Go github.com/QuantumNous/new-api >=0 <1.0.0-rc.11 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6245 (OSV record GO-2026-6245 lists affected ranges: Go github.com/QuantumNous/new-api >=0 <1.0.0-rc.11 (fixed))
- Verified: https://github.com/advisories/GHSA-v828-m3pf-vq9q (GitHub-reviewed advisory GHSA-v828-m3pf-vq9q lists affected ranges: Go github.com/QuantumNous/new-api >=0 <1.0.0-rc.11)

Commands are suggestions: review each one before running it.

Loading voting…