Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-64866

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

Summary

Vulnerability in github.com/QuantumNous/new-api (CVE-2026-64866). Risk of unauthorized operations or information disclosure. Exploitable via DELETE /api/user/. Mitigation: upgrade to 1.0.0-rc.7 or later.

Original description

The description as published by the source.

Summary

The admin passkey reset endpoint lacked the role-level authorization check used by comparable privileged account-protection endpoints. A lower-privileged administrator could attempt passkey reset operations against same-level or higher-privileged users, including root-level accounts.

Impact

If the target account had a passkey configured, a lower-privileged administrator could remove that authentication factor and weaken the target account's protection boundary. The attacker still needed administrator privileges, so the issue is rated Medium.

Affected versions

The vulnerable admin passkey reset behavior was present from the passkey feature introduction in v0.9.1.3 through versions before v1.0.0-rc.7.

Patches

This issue is fixed in v1.0.0-rc.7. The fix adds a canManageTargetRole check to AdminResetPasskey before passkey lookup or deletion, preventing lower-privileged administrators from operating on same-level or higher-privileged users.

Workarounds

If upgrading immediately is not possible, restrict admin access to trusted operators only and block DELETE /api/user/:id/reset_passkey at the reverse proxy or gateway except for root operators.

References

  • Fixed by commit 0936e2504655a5cbf7bc3c388f6d3e2bb24916d3.
  • Relevant code paths: controller/passkey.go, controller/twofa.go, and router/api-router.go.

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-64866 has been found in github.com/QuantumNous/new-api.
Attackers can target a specific entry point like DELETE /api/user/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/QuantumNous/new-api to 1.0.0-rc.7 or later.
If unsure, ask your IT team or search "github.com/QuantumNous/new-api CVE-2026-64866" on the vendor's site.

CVE-2026-64866 (github.com/QuantumNous/new-api) — CWE-862
Attack surface: DELETE /api/user/ / canManageTargetRole / AdminResetPasskey
Patched: 1.0.0-rc.7 — apply immediately
Workaround: If upgrading immediately is not possible, restrict admin access to trusted operators only and block DELETE /api/user/:id/reset_passkey at the reverse proxy or gateway except for root operators.
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-862) exists in github.com/QuantumNous/new-api. Attackers reach the vulnerable code path via DELETE /api/user/.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/QuantumNous/new-api. Attack surface: DELETE /api/user/ / canManageTargetRole / AdminResetPasskey.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.0.0-rc.7.

🛡️ Workaround

Workaround: If upgrading immediately is not possible, restrict admin access to trusted operators only and block DELETE /api/user/:id/reset_passkey at the reverse proxy or gateway except for root operators.

🔍 Detection

Search webserver/proxy logs for unusual DELETE /api/user/ 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 'DELETE /api/user/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply temporary workaround mitigate 
    If upgrading immediately is not possible, restrict admin access to trusted operators only and block `DELETE /api/user/:id/reset_passkey` at the reverse proxy or gateway except for root operators.

    パッチが適用されるまでの応急処置として、If upgrading immediately is not possible, restrict admin access to trusted operators only and block DELETE /api/user/:id/reset_passkey at the reverse proxy or gateway except for root operators. を実施。回避策の副作用 (機能低下) を確認した上で。

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

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

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

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

Affected packages

go github.com/QuantumNous/new-api
[{"type":"ECOSYSTEM","events":[{"introduced":"0.9.1.3"},{"fixed":"1.0.0-rc.7"}]}]

References

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