Summary
New API: Admin can reset passkeys for same-level or higher-privileged users
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.
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.
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, androuter/api-router.go.
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.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2026-64866? CVE-2026-64866 is a medium-severity missing authorization vulnerability in github.com/QuantumNous/new-api (go), affecting versions >= 0.9.1.3, < 1.0.0-rc.7. It is fixed in 1.0.0-rc.7. The application does not perform an authorization check before performing a sensitive operation.
- Which versions of github.com/QuantumNous/new-api are affected by CVE-2026-64866? github.com/QuantumNous/new-api (go) versions >= 0.9.1.3, < 1.0.0-rc.7 is affected.
- Is there a fix for CVE-2026-64866? Yes. CVE-2026-64866 is fixed in 1.0.0-rc.7. Upgrade to this version or later.
- Is CVE-2026-64866 exploitable, and should I be worried? Whether CVE-2026-64866 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-64866 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-64866? Upgrade
github.com/QuantumNous/new-apito 1.0.0-rc.7 or later.