How severe is CVE-2026-64866?

No CVSS score has been assigned to CVE-2026-64866 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-64866?

CVE-2026-64866 affects the following packages: github.com/QuantumNous/new-api (Go). Ecosystems affected: Go.

How do I fix CVE-2026-64866?

Update github.com/QuantumNous/new-api to 1.0.0-rc.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-64866 is resolved across your whole dependency graph.

How do I detect CVE-2026-64866 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/QuantumNous/new-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-64866 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-64866 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-64866 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-64866?

CVE-2026-64866 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-64866?

CVE-2026-64866 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-64866 published, and has it been updated?

CVE-2026-64866 was published on August 17, 2026 and was last updated on September 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

CVE-2026-64866 — new-api

Fix: QuantumNous/new-api@0936e25

CVE-2026-64866 is a CWE-862 vulnerability in github.com/QuantumNous/new-api. A fix is available for github.com/QuantumNous/new-api — see the affected versions and patch details below.

New API: Admin can reset passkeys for same-level or higher-privileged users

Also known asGHSA-p845-629j-rcj6GO-2026-6244

Published

Aug 17, 2026

Updated

Sep 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-64866.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/QuantumNous/new-api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The admin passkey reset endpoint lacked the role-level authorization check used by comparable privileged account-protection endpoints. A lower-privileged administrator could attempt passkey reset operations against same-level or higher-privileged users, including root-level accounts.

Impact

If the target account had a passkey configured, a lower-privileged administrator could remove that authentication factor and weaken the target account's protection boundary. The attacker still needed administrator privileges, so the issue is rated Medium.

Affected versions

The vulnerable admin passkey reset behavior was present from the passkey feature introduction in v0.9.1.3 through versions before v1.0.0-rc.7.

Patches

This issue is fixed in v1.0.0-rc.7. The fix adds a canManageTargetRole check to AdminResetPasskey before passkey lookup or deletion, preventing lower-privileged administrators from operating on same-level or higher-privileged users.

Workarounds

If upgrading immediately is not possible, restrict admin access to trusted operators only and block DELETE /api/user/:id/reset_passkey at the reverse proxy or gateway except for root operators.

References

Fixed by commit 0936e2504655a5cbf7bc3c388f6d3e2bb24916d3.
Relevant code paths: controller/passkey.go, controller/twofa.go, and router/api-router.go.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/QuantumNous/new-api`	≥ 0.9.1.3&&< 1.0.0-rc.7	1.0.0-rc.7`go get github.com/QuantumNous/new-api@v1.0.0-rc.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/QuantumNous/new-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/QuantumNous/new-api to 1.0.0-rc.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-64866 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

## Summary The admin passkey reset endpoint lacked the role-level authorization check used by comparable privileged account-protection endpoints. A lower-privileged administrator could attempt passkey reset operations against same-level or higher-privileged users, including root-level accounts. ## Impact If the target account had a passkey configured, a lower-privileged administrator could remove that authentication factor and weaken the target account's protection boundary. The attacker still needed administrator privileges, so the issue is rated Medium. ## Affected versions The vulnerab

O3 Security · Impact-Aware SCA

Is CVE-2026-64866 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works