CVE-2026-64859

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 61% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 18, 2026

Advisory Details (4)

Auto-updated Sep 16, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

User List API Leaks Root User Access Token Leading to Privilege Escalation · Advisory · QuantumNous/new-api · GitHub

https://github.com/QuantumNous/new-api/security/advisories/GHSA-6x2c-phff-wx57
github_release Patch Available

v1.0.0-rc.7

Patch available: QuantumNous/new-api v1.0.0-rc.7

https://github.com/QuantumNous/new-api/releases/tag/v1.0.0-rc.7
github_pr

perf: avoid eager formatting in debug log calls

Fix merged in QuantumNous/new-api PR #4929 on 2026-05-19 — awaiting tagged release

https://github.com/QuantumNous/new-api/pull/4929
github_commit

commit 0936e2504655 (QuantumNous/new-api)

Fix landed in QuantumNous/new-api commit 0936e2504655 — awaiting tagged release

https://github.com/QuantumNous/new-api/commit/0936e2504655a5cbf7bc3c388f6d3e2bb24916d3

Vendor Advisories for CVE-2026-64859(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/QuantumNous/new-api—1.0.0-rc.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:23 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 21:55 UTCEG score recompute
  4. 2026-09-16 15:16 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:47 UTCEG score recompute
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 04:24 UTCEG score recompute
  9. 2026-09-13 17:25 UTCEG score recompute
  10. 2026-09-12 16:26 UTCEG score recompute
  11. 2026-09-11 15:14 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 11:04 UTCEG score recompute
  14. 2026-09-11 09:37 UTCEPSS rescore
  15. 2026-09-10 09:42 UTCEG score recompute
  16. 2026-09-09 03:41 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 16:11 UTCEG score recompute
  19. 2026-09-07 16:01 UTCEPSS rescore
  20. 2026-09-06 13:53 UTCEG score recompute
  21. 2026-09-06 13:47 UTCEPSS rescore
  22. 2026-09-05 17:00 UTCEG score recompute
  23. 2026-09-05 15:31 UTCEPSS rescore
  24. 2026-09-04 14:12 UTCEG score recompute
  25. 2026-09-04 05:48 UTCEG score recompute
Show 34 more
  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 17:11 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 14:22 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 05:18 UTCEG score recompute
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 20:29 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 03:50 UTCEG score recompute
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-29 05:38 UTCEG score recompute
  13. 2026-08-28 21:42 UTCEPSS rescore
  14. 2026-08-27 15:44 UTCEG score recompute
  15. 2026-08-26 18:40 UTCEG score recompute
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 17:06 UTCEG score recompute
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 15:41 UTCEG score recompute
  20. 2026-08-24 11:32 UTCEG score recompute
  21. 2026-08-23 02:02 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 00:56 UTCEG score recompute
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 23:55 UTCEG score recompute
  26. 2026-08-20 22:55 UTCEPSS rescore
  27. 2026-08-19 18:45 UTCEG score recompute
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 16:58 UTCEG score recompute
  30. 2026-08-18 13:48 UTCEPSS rescore
  31. 2026-08-17 19:27 UTCEG score recompute
  32. 2026-08-17 19:12 UTCEG score recompute
  33. 2026-08-17 16:17 UTCEG score recompute
  34. 2026-08-17 16:17 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64859?
CVE-2026-64859 is a critical vulnerability published on August 17, 2026. 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…
When was CVE-2026-64859 disclosed?
CVE-2026-64859 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64859 actively exploited?
CVE-2026-64859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.6% of all scored CVEs.
What is the CVSS score of CVE-2026-64859?
CVE-2026-64859 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-64859?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64859, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64859

Explore →

Is Your Infrastructure Affected by CVE-2026-64859?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs