# CVE-2026-82909: QuantumNous new-api Revoked API Token token session expiration

> Attackers can bypass session expiration for revoked API tokens, maintaining unauthorized access to the QuantumNous new-api service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-76j5-99cp-jhpp

## What is CVE-2026-82909?

CVE-2026-82909 is a medium-severity vulnerability in QuantumNous new-api, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in QuantumNous new-api up to 1.0.0-rc.15. Affected by this issue is some unknown functionality of the file /api/usage/token/ of the component Revoked API Token Handler. Executing a manipulation can lead to session expiration. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. Upgrading to version 1.0.0-rc.17 can resolve this issue. This patch is called 0d5995eb63f8801d32eb32fbe74b75b68752bfa9. The affected component should be upgraded.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-82909?


## How do I fix CVE-2026-82909?

No fix has been published for CVE-2026-82909 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82909 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82909 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82909 and fix it if it is affected.

What it is: CVE-2026-82909 is a medium-severity vulnerability in QuantumNous new-api, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82909 exists.

Affected product: QuantumNous new-api. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82909/ (Markdown: https://insights.sbomify.com/CVE-2026-82909/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82909
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82909
- OSV: https://osv.dev/vulnerability/CVE-2026-82909

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82909/
Summaries are generated and may contain mistakes; the official description above is the record.