https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T05:12:55.913984+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-277179 EUVD-2026-277179 2026-10-06T05:12:55.973009+00:00 EUVD-2026-277179 https://cve.radiocsirt.org/vuln/fkie_cve-2026-32879 fkie_cve-2026-32879 2026-10-06T05:12:55.973057+00:00

New API is a large language mode (LLM) gateway and artificial intelligence (AI) asset management system. Starting in version 0.10.0, 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. As of time of publication, no known patched versions are available. 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.

 https://cve.radiocsirt.org/vuln/ghsa-5353-f8fq-65vc GHSA-5353-f8fq-65vc — New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure 2026-10-06T05:12:55.973096+00:00

Affected: Go: github.com/QuantumNous/new-api

## 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 no…