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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 4.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N | 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