# CVE-2026-64865: New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass

> An authenticated user can bypass quota limits by racing API requests to overwrite cached quota values in Redis.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-j6gc-4893-qwmp, GO-2026-6243

## What is CVE-2026-64865?

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

### Official description

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.16, repeated PUT /api/user/self requests that update language or sidebar_modules can race relay billing because controller/user.go calls User.Update and updateUserCache performs a full RedisHSetObj write to user:.Quota, overwriting concurrent HINCRBY deductions and allowing an authenticated user to keep cached quota artificially high. This issue is fixed in version 1.0.0-rc.16.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

3 open source packages ship an affected version, including github.com/QuantumNous/new-api.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/QuantumNous/new-api` | Go | All versions | 1.0.0-rc.16 |
| `github.com/QuantumNous/new-api` | Go | All versions | 1.0.0-rc.16 |
| `github.com/QuantumNous/new-api` | Go | All versions | 1.0.0-rc.16 |

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

Upgrade github.com/QuantumNous/new-api to 1.0.0-rc.16 or later.

## Is CVE-2026-64865 being exploited?

There is no known exploitation of CVE-2026-64865 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-64865 is a medium-severity vulnerability in QuantumNous new-api, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-64865 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 1.0.0-rc.16
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 1.0.0-rc.16
- github.com/QuantumNous/new-api (Go): affected all versions; fixed in 1.0.0-rc.16

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-64865/ (Markdown: https://insights.sbomify.com/CVE-2026-64865/index.md)
```

## Sources

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

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