QuantumNous new-api up to 1.0.0-rc.15 Revoked API Token /api/usage/token/ session expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 1.59+ |
Summary
A vulnerability marked as problematic has been reported in QuantumNous new-api up to 1.0.0-rc.15. This affects an unknown part of the file /api/usage/token/ of the component Revoked API Token Handler. The manipulation leads to session expiration. This vulnerability is traded as CVE-2026-82909. It is possible to initiate the attack remotely. Furthermore, there is an exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in QuantumNous new-api up to 1.0.0-rc.15. This issue affects an unknown code of the file /api/usage/token/ of the component Revoked API Token Handler. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-82909. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept.
Upgrading to version 1.0.0-rc.17 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 0d5995eb63f8801d32eb32fbe74b75b68752bfa9 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 1.0.0-rc.0
- 1.0.0-rc.1
- 1.0.0-rc.2
- 1.0.0-rc.3
- 1.0.0-rc.4
- 1.0.0-rc.5
- 1.0.0-rc.6
- 1.0.0-rc.7
- 1.0.0-rc.8
- 1.0.0-rc.9
- 1.0.0-rc.10
- 1.0.0-rc.11
- 1.0.0-rc.12
- 1.0.0-rc.13
- 1.0.0-rc.14
- 1.0.0-rc.15
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Session expirationCWE: CWE-613
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: new-api 1.0.0-rc.17
Patch: 0d5995eb63f8801d32eb32fbe74b75b68752bfa9
Timeline
08/31/2026 Advisory disclosed08/31/2026 VulDB entry created
08/31/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-82909 (🔒)
GCVE (CVE): GCVE-0-2026-82909
GCVE (VulDB): GCVE-100-397289
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/31/2026 12:16Changes: 08/31/2026 12:16 (61)
Complete: 🔍
Submitter: yaowenxiao
Cache ID: 216::103
Submit
Accepted
- Submit #877769: QuantumNous new-api v1.0.0-rc.15 Insufficient Session Expiration (by yaowenxiao)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.