CVE-2026-64865
Received Received - Intake

Race Condition in New API LLM Gateway Leading to Quota Bypass

Publication date: 2026-08-17

Last updated on: 2026-08-17

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-17
Last Modified
2026-08-17
Generated
2026-08-17
AI Q&A
2026-08-17
EPSS Evaluated
N/A
NVD
CVE-2026-64865
EUVD
EUVD-2026-60263

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
quantumnous new-api 1.0.0-rc.16

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-362 The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-64865 is a race condition vulnerability in the New API project, an LLM gateway and AI asset management system. It occurs when repeated PUT requests to update user settings (like language or sidebar modules) race with quota deductions in Redis. The system overwrites the Redis quota cache with a stale full user snapshot, erasing concurrent quota deductions and inflating the cached balance.

Detection Guidance

Check for repeated PUT /api/user/self requests updating language or sidebar_modules fields. Monitor Redis for HSET operations overwriting user:.Quota fields during concurrent quota deductions. Review logs for users with artificially high cached quota balances despite active usage.

Impact Analysis

This vulnerability allows authenticated users to bypass quota enforcement by artificially inflating their cached quota balance. This can lead to financial loss for operators who rely on accurate quota tracking for billing or resource allocation. Users could consume more resources than permitted without detection.

Compliance Impact

This vulnerability allows authenticated users to artificially inflate their cached quota balance by exploiting a race condition, potentially bypassing billing and resource limits. This could lead to unauthorized resource usage or financial loss for operators. While not directly violating GDPR or HIPAA, such a flaw could undermine compliance by enabling unauthorized data processing or resource consumption if quota limits are tied to service tiers or access controls.

Mitigation Strategies

Upgrade to version 1.0.0-rc.16 or later. Temporarily restrict access to PUT /api/user/self endpoint. Implement rate limiting on the self-update endpoint. Monitor Redis cache operations to prevent HSET overwrites of quota fields.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-64865. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart