CVE-2026-64859: New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Prior to 1.0.0-rc.7, the admin user list and user lookup APIs, including GET /api/user/, return User.AccessToken as access_token because User model objects are serialized after queries use Omit("password"), allowing an authenticated administrator to obtain the root user's bearer token and access root-only system configuration APIs. This issue is fixed in version 1.0.0-rc.7.
Security readout for executives and security teams
Plain-English summary
An authenticated administrator can retrieve the root user's bearer token from New API's user-management responses. That token can grant access to root-only configuration functions, turning a compromised or malicious administrator account into full system control. Versions before 1.0.0-rc.7 are affected.
Executive priority
Treat as an immediate remediation priority for affected deployments. Upgrade promptly, investigate historical administrative API access, and rotate the root token where supported. The administrative prerequisite reduces broad opportunistic exposure, but successful abuse could provide root-level control over an AI gateway and its configuration.
Technical view
New API serialized User model objects after queries excluded only the password field. Consequently, admin user-list and lookup responses, including GET /api/user/, exposed User.AccessToken as access_token. An authenticated administrator could reuse the root token against root-only configuration APIs. Version 1.0.0-rc.7 fixes the disclosure.
Likely exposure
Exposure exists where QuantumNous New API earlier than 1.0.0-rc.7 is deployed and an administrator can access the affected user APIs. Internet exposure increases account-compromise opportunity, but exploitation still requires authenticated administrator privileges according to the supplied CVSS vector.
Exploitation context
The supplied record reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation requires administrator authentication, but the disclosed root bearer token can cross a privilege boundary without user interaction, with potentially severe confidentiality, integrity, and availability impact.
Researcher notes
CWE-200 applies because sensitive authentication material was included in serialized API output. CVSS 3.1 is 9.1: network-accessible, low complexity, high privileges required, no user interaction, changed scope, and high impact across confidentiality, integrity, and availability. The supplied evidence does not establish public exploitation or identify affected versions beyond releases before 1.0.0-rc.7.
Mitigation direction
Upgrade QuantumNous New API to version 1.0.0-rc.7 or later.
After upgrading, rotate the root access token if supported by documented vendor procedures.
Review administrator accounts and revoke access that is unnecessary or suspicious.
Restrict administrative API access while upgrades and credential rotation are completed.
Consult the vendor advisory for deployment-specific remediation guidance.
Validation and detection
Inventory New API instances and confirm each running version.
Verify no deployed instance is earlier than 1.0.0-rc.7.
Confirm user-list and lookup responses no longer contain access_token values.
Review logs for administrator requests to affected user-management endpoints before remediation.
Check for unexpected root-only configuration activity following those requests.
Confirm any potentially exposed root token has been invalidated.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-200 · source CWE mapping
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.