Account credit inflation via quota overflow
Published Aug 17, 2026 · Updated Aug 17, 2026
Integer overflow in billing paths in QuantumNous New API before 1.0.0-rc.18 allows remote authenticated users to inflate account credit. Request fields such as image n, video duration, max_tokens, max_completion_tokens, maxOutputTokens, audio duration, and billing-expression quantities are multiplied into quota math in common/quota_math.go and related settlement code and then converted to int without safe bounds, so oversized values wrap into negative charges that post as credits. Exploitation requires an account with positive balance or an active subscription; where self-registration and free starter quota are enabled, a single crafted request can mint spendable balance and expose upstream funds to drain.
Summary
What happened
Integer overflow in billing paths in QuantumNous New API before 1.0.0-rc.18 allows remote authenticated users to inflate account credit. Request fields such as image n, video duration, max_tokens, max_completion_tokens, maxOutputTokens, audio duration, and billing-expression quantities are multiplied into quota math in common/quota_math.go and related settlement code and then converted to int without safe bounds, so oversized values wrap into negative charges that post as credits. Exploitation requires an account with positive balance or an active subscription; where self-registration and free starter quota are enabled, a single crafted request can mint spendable balance and expose upstream funds to drain.
The record
- CVE
- CVE-2026-71479
- Published
- Aug 17, 2026
- Updated
- Aug 17, 2026
- Vendor
- QuantumNous
- Product
- New API
- Classifications
- CWE-190, CWE-682, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 6, 2026Exploitation reportedQuantumNous advisory reports in-the-wild exploitation
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.0.0-rc.18
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- QuantumNous advisory reports in-the-wild exploitationreported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo