INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-64859

New API: User List API Leaks Root User Access Token Leading to Privilege Escalation

CVE-2026-64859 ยท 2026-08-17 critical

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Information exposure
Affected
github.com/QuantumNous/new-api (Go)
Gets past
Authorisation check
CVSS
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6% chance of exploitation in 30 days

How it works, in short

The admin user list API serialises each user's access token, so an admin can read the root account's bearer token and act as root. (Our summary, written by a model. The source text is below.)

Details

Vulnerability Information

Description

In affected versions of new-api, the admin user list and user lookup APIs can return the access_token field for users, including the root user. An authenticated admin user can call endpoints such as GET /api/user/ to retrieve user records. Because access tokens function as bearer credentials for API authentication, leaking the root user's access token allows an admin user to authenticate as root and access root-only endpoints such as system configuration APIs.

This bypasses the intended role boundary between admin users and the root user and can result in privilege escalation to full system control.

Root Cause

The User.AccessToken field was serialized as json:"access_token" in affected versions. User management APIs returned User model objects directly after omitting only the password field from database queries, so JSON serialization could include access_token in API responses.

Affected code patterns include user list, user search, and user detail paths that use Omit("password") without preventing access_token from being serialized.

Impact

Remediation

Upgrade to v1.0.0-rc.7 or later. The fix changes User.AccessToken to use json:"-", preventing the field from being serialized in API responses.

Operators should also rotate any root or user access tokens that may have been exposed before upgrading, especially if untrusted admin users had access to user management APIs.

References

Source: GitHub Advisory Database, used under CC BY 4.0.