CVE-2026-71479

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.18, user-controlled image n, video seconds and duration, max_tokens, max_completion_tokens, maxOutputTokens, audio duration, and billing-expression quantities can overflow conversions in common/quota_math.go and related settlement paths, allowing a low-privileged account with positive balance or an active subscription to turn a negative charge into account credit and potentially drain upstream funds. This issue is fixed in version 1.0.0-rc.18.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Integer overflow in quota billing yields negative charges (self-crediting) · Advisory · QuantumNous/new-api · GitHub

https://github.com/QuantumNous/new-api/security/advisories/GHSA-8r8v-xf7q-rcpr
github_release Patch Available

v1.0.0-rc.18

Patch available: QuantumNous/new-api v1.0.0-rc.18

https://github.com/QuantumNous/new-api/releases/tag/v1.0.0-rc.18
github_commit

commit d0bd8aac742d (QuantumNous/new-api)

Fix landed in QuantumNous/new-api commit d0bd8aac742d — awaiting tagged release

https://github.com/QuantumNous/new-api/commit/d0bd8aac742d1e160a5ca61743fe35f4fff880e8
github_commit

commit c9943d37ad93 (QuantumNous/new-api)

Fix landed in QuantumNous/new-api commit c9943d37ad93 — awaiting tagged release

https://github.com/QuantumNous/new-api/commit/c9943d37ad93477dd937fc4901cc3c4e0fd8aaab

Vendor Advisories for CVE-2026-71479(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/QuantumNous/new-api—1.0.0-rc.18—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:21 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:55 UTCEG score recompute
  4. 2026-09-16 15:16 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:40 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 04:16 UTCEG score recompute
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-13 16:50 UTCEG score recompute
  11. 2026-09-12 16:11 UTCEG score recompute
  12. 2026-09-12 15:02 UTCEPSS rescore
  13. 2026-09-11 15:11 UTCEG score recompute
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 11:04 UTCEG score recompute
  16. 2026-09-10 09:42 UTCEG score recompute
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-09 03:40 UTCEG score recompute
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-07 16:11 UTCEG score recompute
  21. 2026-09-06 17:39 UTCEG score recompute
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-05 16:44 UTCEG score recompute
  24. 2026-09-04 14:08 UTCEG score recompute
  25. 2026-09-04 05:48 UTCEG score recompute
Show 35 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 17:11 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 14:22 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 05:18 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 20:13 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 03:42 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 05:32 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 15:30 UTCEG score recompute
  15. 2026-08-26 18:53 UTCEG score recompute
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 13:59 UTCEG score recompute
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 17:08 UTCEG score recompute
  20. 2026-08-24 12:30 UTCEG score recompute
  21. 2026-08-23 03:36 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 02:59 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 02:21 UTCEG score recompute
  26. 2026-08-20 22:56 UTCEPSS rescore
  27. 2026-08-19 20:46 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 15:58 UTCEG score recompute
  30. 2026-08-18 13:49 UTCEPSS rescore
  31. 2026-08-18 13:49 UTCEPSS rescore
  32. 2026-08-17 19:27 UTCEG score recompute
  33. 2026-08-17 19:12 UTCEG score recompute
  34. 2026-08-17 16:22 UTCEG score recompute
  35. 2026-08-17 16:22 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71479?
CVE-2026-71479 is a critical vulnerability published on August 17, 2026. New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.18, user-controlled image n, video seconds and duration, maxtokens, maxcompletiontokens, maxOutputTokens, audio duration, and billing-expression quantities can overflow…
When was CVE-2026-71479 disclosed?
CVE-2026-71479 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71479 actively exploited?
CVE-2026-71479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.9% of all scored CVEs.
What is the CVSS score of CVE-2026-71479?
CVE-2026-71479 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-71479?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71479, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71479

Explore →

Is Your Infrastructure Affected by CVE-2026-71479?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs