Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-64868 high CVSS 7.5

Vulnerability in github.com/QuantumNous/new-api (CVE-2026-64868)

Summary

Vulnerability in github.com/QuantumNous/new-api (CVE-2026-64868). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/stripe/webhook. Mitigation: upgrade to 1.0.0-rc.11 or later.

Original description

The description as published by the source.

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,…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-64868 has been found in github.com/QuantumNous/new-api.
Attackers can target a specific entry point like POST /api/stripe/webhook over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/QuantumNous/new-api to 1.0.0-rc.11 or later.
If unsure, ask your IT team or search "github.com/QuantumNous/new-api CVE-2026-64868" on the vendor's site.

CVE-2026-64868 (github.com/QuantumNous/new-api) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/stripe/webhook / POST /api/creem/webhook / POST /api/waffo/webhook / ANONYMOUS_REQUEST_BODY_LIMIT_KB
Patched: 1.0.0-rc.11 — apply immediately
Workaround: 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.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-400) exists in github.com/QuantumNous/new-api. Attackers reach the vulnerable code path via POST /api/stripe/webhook without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/QuantumNous/new-api. Attack surface: POST /api/stripe/webhook / POST /api/creem/webhook / POST /api/waffo/webhook / ANONYMOUS_REQUEST_BODY_LIMIT_KB.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.0-rc.11.

🛡️ Workaround

Workaround: 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.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/stripe/webhook requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/QuantumNous/new-api' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/QuantumNous/new-api' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/QuantumNous/new-api を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/stripe/webhook' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/stripe/webhook への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply temporary workaround mitigate 
    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.

    パッチが適用されるまでの応急処置として、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. を実施。回避策の副作用 (機能低下) を確認した上で。

  4. 4
    Apply patch patch 
    Upgrade github.com/QuantumNous/new-api to 1.0.0-rc.11

    ステージング環境で 1.0.0-rc.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  5. 5
    Post-deployment verification verify 
    Replay attack against POST /api/stripe/webhook on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

go github.com/QuantumNous/new-api
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.0.0-rc.11"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details