Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.1amended

New API: Integer overflow in quota billing yields negative charges (self-crediting)

CVE-2026-71479GHSA-8r8v-xf7q-rcpr

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/QuantumNous/new-api 1.0.0-rc.18), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
EPSS
  • CVE-2026-71479: 0.65% estimated exploitation activity in the next 30 days; percentile 51.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-8r8v-xf7q-rcpr

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6242

  3. Revision 1 · created ·

    Published from osv record GHSA-8r8v-xf7q-rcpr

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71479

Advisory: New API: Integer overflow in quota billing yields negative charges (self-crediting)
IDs: CVE-2026-71479, GHSA-8r8v-xf7q-rcpr
Record: https://patchnext.com/advisories/cve-2026-71479 (revision 3, source checked 26 Oct 2026, 15:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/QuantumNous/new-api 1.0.0-rc.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/QuantumNous/new-api: affected <= 1.0.0-rc.17; fixed in 1.0.0-rc.18

## Suggested inspection (read-only)
- Go github.com/QuantumNous/new-api: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/QuantumNous/new-api.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8r8v-xf7q-rcpr (OSV record GHSA-8r8v-xf7q-rcpr lists affected ranges: Go github.com/QuantumNous/new-api >=0 <1.0.0-rc.18 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6242 (OSV record GO-2026-6242 lists affected ranges: Go github.com/QuantumNous/new-api >=0 <1.0.0-rc.18 (fixed))
- Verified: https://github.com/advisories/GHSA-8r8v-xf7q-rcpr (GitHub-reviewed advisory GHSA-8r8v-xf7q-rcpr lists affected ranges: Go github.com/QuantumNous/new-api >=0 <=1.0.0-rc.17)

Commands are suggestions: review each one before running it.

Loading voting…