LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A billing calculation flaw in New API can turn oversized, user-controlled usage values into negative charges. Instead of reducing an account balance, the system may add credit, enabling fraudulent consumption and potentially exhausting upstream provider funds. QuantumNous fixed the issue in version 1.0.0-rc.18.

Executive priority

Treat this as an immediate financial-integrity issue. Prioritize upgrading exposed billing gateways, then review historical transactions and upstream provider spending. Escalate any unexplained credits or consumption spikes because the vulnerability may directly convert application access into monetary loss and service disruption.

Technical view

Before 1.0.0-rc.18, integer conversion overflows in common/quota_math.go and related settlement paths can corrupt charges for image, video, token, audio, and billing-expression quantities. An account with positive balance or an active subscription may receive credit from a negative charge, compromising billing integrity and potentially service availability.

Likely exposure

Internet-accessible New API deployments below 1.0.0-rc.18 are potentially exposed where users can submit affected quantity fields and trigger settlement. Practical abuse appears to require a usable account with positive balance or an active subscription, despite the supplied CVSS vector recording no privileges required.

Exploitation context

The supplied record is not in CISA KEV, and the cited sources provide no evidence of active exploitation. Exploitation is nevertheless plausible because affected quantities are user-controlled, attack complexity is rated low, and successful abuse could create credit or consume upstream funds.

Researcher notes

The affected surface spans multiple quantity conversions and settlement paths, not one endpoint. Review both referenced commits and regression coverage for overflow-safe conversions, sign handling, boundary validation, and billing expressions. The public evidence establishes impact and a fixed release but does not establish exploitation in the wild.

Mitigation direction

  • Upgrade QuantumNous New API to version 1.0.0-rc.18 or later.
  • Until upgraded, strictly cap affected quantity fields to documented safe ranges.
  • Restrict account creation and subscription activation where operationally feasible.
  • Monitor and suspend accounts showing negative charges or unexplained balance increases.

Validation and detection

  • Inventory deployed New API versions and identify every instance below 1.0.0-rc.18.
  • Confirm all production instances run the fixed release or later.
  • Review billing records for negative charges, unexpected credits, and abnormal upstream consumption.
  • Verify affected quantity fields reject values outside approved operational ranges.
  • Confirm settlement calculations cannot increase balances when recording billable usage.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-682: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-71479 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H3.95.2GitHub_M

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-71479Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
QuantumNousnew-api< 1.0.0-rc.18Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.