# New API has passkey-based secure step-up verification bypass for root-only channel secret disclosure

Advisory record · `GHSA-5353-f8fq-65vc`

- **Identifiers:** `GHSA-5353-f8fq-65vc` · `CVE-2026-32879` · `GO-2026-4813`
- **State:** Confirmed
- **Severity:** CVSS 4.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 23 Mar 2026
- **Updated:** 30 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Mar 2026, 19:56 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/QuantumNous/new-api` (Go): affected `>=0.10.0, <=0.11.9-alpha.1`; no fixed version yet

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> New API versions 0.10.0 through 0.11.9-alpha.1 are affected, and no fixed version is listed. An authenticated user with a registered passkey can satisfy the secure verification step-up without completing a WebAuthn assertion. The source identifies the root-only channel key endpoint, which returns stored channel secrets, as the confirmed impact. Until a patch is available, the source suggests avoiding passkey as the step-up method and requiring TOTP/2FA instead.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 4.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0033, the 26th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:08 UTC: First seen by agentprime
- 31 Oct 2026, 15:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-5353-f8fq-65vc)

## Sources

- [GitHub Advisory Database: GHSA-5353-f8fq-65vc](https://github.com/advisories/GHSA-5353-f8fq-65vc)
- [OSV: GHSA-5353-f8fq-65vc](https://osv.dev/vulnerability/GHSA-5353-f8fq-65vc)
- <https://github.com/QuantumNous/new-api/security/advisories/GHSA-5353-f8fq-65vc>
- <https://github.com/QuantumNous/new-api>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5353-f8fq-65vc>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5353-f8fq-65vc/>. Everything for agents: <https://agentprime.io/llms.txt>.
