vulns.co
/
GKData.io MCP and API Buy me a coffee

USENIX Association

Adversarial passkeys: account recovery must close every continuing source of authority

In a lab study of 31 people across three services, unclear passkey labels, notifications and recovery screens prevented complete account recovery without help. The scenario assumed earlier account access sufficient to register a credential, rather than a break in passkey cryptography. The small controlled study highlights the need to revoke credentials and sessions separately; it does not measure real-world compromise rates or validate the proposed interface improvements.

Open the referenceResearch PaperReviewed 2026-10-03

How to use this reference

Review an owned application’s recovery completion criteria across registered credentials, sessions and recovery channels. Make security interfaces explain what each revocation changes and what remains authorized; use clear credential provenance and action-specific notifications. Treat these as design-review questions, not evidence of a deployed fix.

Before reading

  • Passkey registration and relying-party credential records
  • Session invalidation and account-recovery concepts

Context and limits

  • The simulated scenario presupposes earlier account access sufficient to register a credential; one service additionally required an email challenge. This is not a cryptographic break of passkeys or evidence of unauthenticated access.
  • The paper reports that no participant completed all required remediation unaided. This demonstrates usability failures in controlled test accounts, not population-wide compromise rates or current service exposure.
  • The small, single-city sample used researcher-provided devices and accounts; researcher assistance limits generalization of success rates.
  • The authors explicitly label proposed interface improvements speculative and needing validation. Password reset, credential removal and session termination have distinct effects.
  • This is a conference proceedings research paper, not a vendor patch advisory; no fixed-version claim is made.

Sources

  1. “Maybe there’s only one passkey?”: Challenges Investigating and Remediating Adversarial PasskeysUSENIX Association · reviewed 2026-10-03
  2. Publisher-hosted proceedings paperUSENIX Association · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software