CVE-2026-32879: New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure
Summary A logic flaw in the universal secure verification flow allows an authenticated user with a registered passkey to satisfy secure verification without completing a WebAuthn assertion. Affected versions = v0.10.0 Description The POST /api/verify endpoint supports multiple secure verification methods, including passkeys.
Published Mar 23, 2026 · Updated Mar 30, 2026
Affected packages
github.com/QuantumNous/new-api
- Ecosystem
- Go
- Affected
- >= 0.10.0, <= 0.11.9-alpha.1
- Fixed in
- No patched version yet
- Check
go list -m github.com/QuantumNous/new-api
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A logic flaw in the universal secure verification flow allows an authenticated user with a registered passkey to satisfy secure verification without completing a WebAuthn assertion.
Affected versions
= v0.10.0
Description
The POST /api/verify endpoint supports multiple secure verification methods, including passkeys. When the request body contains {"method":"passkey"}, the server only checks whether the authenticated account has a passkey record on file and then marks the secure verification session as complete. It does not verify that the requester successfully completed a WebAuthn assertion.
As a result, an authenticated user who already has a valid session and a registered passkey can satisfy the secure verification requirement without performing the intended passkey challenge/response flow.
Impact
In the upstream project, this issue affects actions protected by SecureVerificationRequired(). At the time of publication, the confirmed upstream impact is the root-only POST /api/channel/:id/key endpoint, which returns stored channel secrets.
Successful exploitation requires:
- an already authenticated session for the target account, and
- a registered passkey on that account.
No full login bypass or cross-account privilege escalation has been confirmed in the upstream codebase. However, the issue defeats the intended step-up verification control for affected privileged actions.
Workarounds
Until a patched release is applied:
- do not rely on passkey as the step-up method for privileged secure-verification actions;
- require TOTP/2FA for those actions where operationally possible; or
- temporarily restrict access to affected secure-verification-protected endpoints.
Credited to asdf2adsfad, seefs001.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-64859
New API: User List API Leaks Root User Access Token Leading to Privilege Escalation
critical9.1Aug 17, 2026CVE-2026-64865
New API: Redis user quota cache overwrite via PUT /api/user/self allows quota bypass
medium6.0Aug 17, 2026CVE-2026-64866
New API: Admin can reset passkeys for same-level or higher-privileged users
medium5.1Aug 17, 2026CVE-2026-64868
New API: Unauthenticated payment webhooks allow memory and disk DoS via unbounded body reads and full-body logging
high7.5Aug 17, 2026CVE-2026-71479
New API: Integer overflow in quota billing yields negative charges (self-crediting)
critical9.1Aug 17, 2026CVE-2026-33655
New API: SSRF Protection Bypass via Unresolved Hostname in Notification URLs
high7.7Jul 7, 2026
