https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 05 Oct 2026 21:56:11 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-354992 EUVD-2026-354992 https://cve.radiocsirt.org/vuln/euvd-2026-354992 https://cve.radiocsirt.org/vuln/fkie_cve-2026-64865 <p>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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-64865 https://cve.radiocsirt.org/vuln/ghsa-j6gc-4893-qwmp <p><strong>Affected:</strong> Go: github.com/QuantumNous/new-api</p> <p>### 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.</p> <p>### 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.</p> <p>### 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</p> <p>### Root Cause Normal billing uses Redis HINCRBY on user:&lt;id&gt;.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.</p> <p>### 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.</p> <p>### Workarounds…</p> <p><strong>Affected:</strong> Go: github.com/QuantumNous/new-api</p> <p>### 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.</p> <p>### 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.</p> <p>### 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</p> <p>### Root Cause Normal billing uses Redis HINCRBY on user:&lt;id&gt;.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.</p> <p>### 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.</p> <p>### Workarounds…</p> https://cve.radiocsirt.org/vuln/ghsa-j6gc-4893-qwmp