← Back
CVE-2026-41432
high
CVSS 7.1
Vulnerability in github.com/QuantumNous/new-api (CVE-2026-41432)
Summary
vulnerability in github.com/QuantumNous/new-api (CVE-2026-41432). Data can be tampered with by attackers. Exploitable via `POST /api/user/pay`. Mitigation: upgrade to `0.12.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41432** has been found in github.com/QuantumNous/new-api.
Attackers can target a specific entry point like `POST /api/user/pay` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade github.com/QuantumNous/new-api to **0.12.10** or later.
If unsure, ask your IT team or search "github.com/QuantumNous/new-api CVE-2026-41432" on the vendor's site.
CVE-2026-41432 (github.com/QuantumNous/new-api) — CWE-345 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/user/pay / GET /api/user/topup/self / POST /api/stripe/webhook / `StripeWebhookSecret`
Patched: `0.12.10` — apply immediately
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-345) exists in github.com/QuantumNous/new-api. Attackers reach the vulnerable code path via `POST /api/user/pay` without authentication.
📍 Affected scope
github.com/QuantumNous/new-api — . Attack surface: POST /api/user/pay / GET /api/user/topup/self / POST /api/stripe/webhook / `StripeWebhookSecret`.
🔥 Severity
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **0.12.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /api/user/pay` 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 (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/user/pay' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/user/pay` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade github.com/QuantumNous/new-api to 0.12.10ステージング環境で 0.12.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/user/pay on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/QuantumNous/new-api
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.12.10"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41432
- exploit 134c704f-9b21-4f2e-91b3-4a467353bcc0
- package https://github.com/QuantumNous/new-api
- web [email protected]
- web https://docs.stripe.com/checkout/fulfillment#async-payment-methods
- web https://docs.stripe.com/webhooks#verify-official-libraries
- web https://github.com/advisories/GHSA-xff3-5c9p-2mr4