github.com/QuantumNous/new-api
Affected
- introduced
0, fixed1.0.0-rc.7(semver)
Fixed versions
1.0.0-rc.7
Fix
- Fixed version
1.0.0-rc.7go get github.com/QuantumNous/[email protected]
Advisory
Also known as: CVE-2026-64859, GO-2026-6240
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
Vulnerability Information
v1.0.0-rc.7 that serialize User.AccessToken as access_token; the issue was confirmed in v0.12.14v1.0.0-rc.70936e2504655a5cbf7bc3c388f6d3e2bb24916d3Description
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.
Critical Basis: The source's own band: CRITICAL
0, fixed 1.0.0-rc.7 (semver)1.0.0-rc.7
1.0.0-rc.7go get github.com/QuantumNous/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0