Is github.com/QuantumNous/new-api 0.12 vulnerable?
Go · 16 releases from 0.12.0 to 0.12.15 · latest github.com/QuantumNous/new-api is 0.13.2 · checked 18 Nov 2026
Yes: 13 known advisories
Yes. github.com/QuantumNous/new-api 0.12.15, the last 0.12 release, is affected by 13 known security advisories (2 critical, 1 high, 2 medium, 8 low), including CVE-2026-71479, CVE-2026-64859, CVE-2026-64868. 2 more affect earlier 0.12.x releases. At least one has no fixed release yet.
Is your project on an affected github.com/QuantumNous/new-api?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting github.com/QuantumNous/new-api 0.12.15
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation in github.com/QuantumNous/new-api
- Affected
- <1.0.0-rc.7
- Fixed in
- 1.0.0-rc.7
New API: Integer overflow in quota billing yields negative charges (self-crediting) in github.com/QuantumNous/new-api
- Affected
- <1.0.0-rc.18
- Fixed in
- 1.0.0-rc.18
New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass in github.com/QuantumNous/new-api
- Affected
- <1.0.0-rc.16
- Fixed in
- 1.0.0-rc.16
New API: Admin can reset passkeys for same-level or higher-privileged users in github.com/QuantumNous/new-api
- Affected
- <1.0.0-rc.7
- Fixed in
- 1.0.0-rc.7
New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging in github.com/QuantumNous/new-api
- Affected
- <1.0.0-rc.11
- Fixed in
- 1.0.0-rc.11
New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass
- Affected
- <1.0.0-rc.16
- Fixed in
- 1.0.0-rc.16
New API: Integer overflow in quota billing yields negative charges (self-crediting)
- Affected
- <1.0.0-rc.18
- Fixed in
- 1.0.0-rc.18
New API: Admin can reset passkeys for same-level or higher-privileged users
- Affected
- >=0.9.1.3 <1.0.0-rc.7
- Fixed in
- 1.0.0-rc.7
New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
- Affected
- <1.0.0-rc.11
- Fixed in
- 1.0.0-rc.11
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
- Affected
- <1.0.0-rc.7
- Fixed in
- 1.0.0-rc.7
QuantumNous/new-api has an SSRF Filter Bypass via 0.0.0.0 in github.com/QuantumNous/new-api
- Affected
- All versions
- Fixed in
- No fix released
New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure in github.com/QuantumNous/new-api
- Affected
- >=0.10.0
- Fixed in
- No fix released
new-api is vulnerable to SSRF Bypass in one-api
- Affected
- All versions
- Fixed in
- No fix released
Fixed within 0.12.x, affecting earlier releases
New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud in github.com/QuantumNous/new-api
- Affected
- <0.12.10
- Fixed in
- 0.12.10
New API: Stripe Webhook Signature Bypass via Empty Secret Enables Unlimited Quota Fraud
- Affected
- <0.12.10
- Fixed in
- 0.12.10
Every github.com/QuantumNous/new-api 0.12.x release
Affected: 0.12.0 to 0.12.15. Latest github.com/QuantumNous/new-api: 0.13.2.
| Version | Known advisories |
|---|---|
| github.com/QuantumNous/new-api 0.12.15 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.14 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.13 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.12 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.11 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.10 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-42339, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.9 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.8 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.7 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.6 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.5 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.4 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.3 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.2 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.1 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
| github.com/QuantumNous/new-api 0.12.0 | CVE-2026-64859, CVE-2026-71479, CVE-2026-64865, CVE-2026-64866, CVE-2026-64868, CVE-2026-64865, CVE-2026-71479, CVE-2026-64866, CVE-2026-64868, CVE-2026-64859, CVE-2026-41432, CVE-2026-42339, CVE-2026-41432, CVE-2026-32879, CVE-2025-62155 |
Which of your client projects are still on github.com/QuantumNous/new-api 0.12?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact github.com/QuantumNous/new-api version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other github.com/QuantumNous/new-api versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.