CVE-2026-64865: New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass
Summary Authenticated users can repeatedly call PUT /api/user/self with language or sidebarmodules while relay requests are consuming quota. The settings path reads a full User snapshot and writes it back through User.Update(), which refreshes Redis with RedisHSetObj and overwrites the Quota field.
Published Aug 17, 2026
Affected packages
github.com/QuantumNous/new-api
- Ecosystem
- Go
- Affected
- <= 1.0.0-rc.15
- Fixed in
- 1.0.0-rc.16
- Check
go list -m github.com/QuantumNous/new-api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Authenticated users can repeatedly call PUT /api/user/self with language or sidebar_modules while relay requests are consuming quota. The settings path reads a full User snapshot and writes it back through User.Update(), which refreshes Redis with RedisHSetObj and overwrites the Quota field. This can erase concurrent HINCRBY quota deductions and keep cached balance artificially high, allowing calls far beyond the paid quota.
Impact
A low-privileged authenticated user may bypass quota enforcement and cause financial loss to operators. Authentication and pre-consumption use cached quota, while DB/log usage can continue increasing.
Affected Components
- controller/user.go: UpdateSelf language/sidebar_modules branches
- model/user.go: User.Update / UpdateWithTx full snapshot update
- model/user_cache.go: updateUserCache RedisHSetObj full hash write
- model/user.go: GetUserQuota reads Redis cache first
Root Cause
Normal billing uses Redis HINCRBY on user:.Quota, while settings updates use a stale full user snapshot to HSET the entire cache hash, including Quota. These two writers race on the same Redis field.
Patches
This issue is fixed in v1.0.0-rc.16. The fix makes user setting updates field-scoped, prevents stale user snapshots from overwriting accounting fields, and keeps generic user cache refreshes from modifying Quota. Quota cache updates are reserved for atomic quota delta paths or explicit quota synchronization paths.
Workarounds
If upgrading immediately is not possible, operators should temporarily restrict or rate-limit PUT /api/user/self and avoid allowing frequent user setting updates while Redis-backed quota cache is enabled. This is only a mitigation; upgrading is recommended.
Remediation
Upgrade to v1.0.0-rc.16 or later. Deployments with Redis enabled should restart application instances after upgrading so stale in-process code paths are removed.
Credited to lihui12388.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-64859
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
critical9.1Aug 17, 2026CVE-2026-64866
New API: Admin can reset passkeys for same-level or higher-privileged users
medium5.1Aug 17, 2026CVE-2026-64868
New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
high7.5Aug 17, 2026CVE-2026-71479
New API: Integer overflow in quota billing yields negative charges (self-crediting)
critical9.1Aug 17, 2026CVE-2026-33655
New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs
high7.7Jul 7, 2026CVE-2026-44342
New API is vulnerable to CSRF through user email binding
medium5.3Jul 7, 2026
