Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-71479 critical CVSS 9.1

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

Summary

Vulnerability in github.com/QuantumNous/new-api (CVE-2026-71479). Data can be tampered with by attackers. Exploitable via CheckinSetting.Enabled. Mitigation: upgrade to 1.0.0-rc.18 or later.

Original description

The description as published by the source.

Summary

Multiple billing paths multiplied user-controlled quantity parameters into the quota calculation without an upper bound or overflow-safe integer conversion. A crafted extreme value (e.g. image n = 18446744073686646784, a wrapped-negative accepted by a *uint field) makes conversions like int(float64(quota) * n) wrap past the int64/int32 range into a large negative quota. The negative quota takes effect at settlement (not at pre-consume), where it is equivalent to crediting the user's balance — turning a small positive balance into an enormous one.

Timeline（UTC+8）

This vulnerability was confirmed exploited in the wild. Response timeline (UTC+8):

  • 2026-07-06 23:00 — Community user @lihui12388 reported that their deployment had been exploited via this vulnerability (large negative consumption entries in logs and abnormally inflated balances). We confirmed in-the-wild exploitation and started an emergency response immediately.
  • 2026-07-07 01:17 — Emergency fix released as v1.0.0-rc.18, roughly 2 hours after the report.
  • 2026-07-07 (next day) — Given the confirmed active exploitation, we publicly disclosed the vulnerability and the fixed version to the community the following day so that all operators could upgrade and audit promptly.
  • 2026-07-07 13:19 — v1.0.0-rc.19 released with ad…

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-71479 has been found in github.com/QuantumNous/new-api.
Attackers can target a specific entry point like CheckinSetting.Enabled over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade github.com/QuantumNous/new-api to 1.0.0-rc.18 or later.
If unsure, ask your IT team or search "github.com/QuantumNous/new-api CVE-2026-71479" on the vendor's site.

CVE-2026-71479 (github.com/QuantumNous/new-api) — CWE-190 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: CheckinSetting.Enabled / QuotaForInviter / QuotaForInvitee / QuotaForNewUser
Patched: 1.0.0-rc.18 — 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-190) exists in github.com/QuantumNous/new-api. Attackers reach the vulnerable code path via CheckinSetting.Enabled without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/QuantumNous/new-api. Attack surface: CheckinSetting.Enabled / QuotaForInviter / QuotaForInvitee / QuotaForNewUser.

🔥 Severity

Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.0.0-rc.18.

🛡️ 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 request patterns matching this CVE's known IOCs. 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
    Apply patch patch 
    Upgrade github.com/QuantumNous/new-api to 1.0.0-rc.18

    ステージング環境で 1.0.0-rc.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

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

Affected packages

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

References

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