CVE-2025-71400: better-auth passkey · Insecure Direct Object Reference
Affects better-auth passkeySource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 1.4.0 soon.
Data as of 31 Oct 2026, 08:20 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade better-auth passkey to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| better-authpasskey | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict access to the passkey deletion endpoint to trusted users only and monitor for suspicious deletion activities. Avoid exposing passkey IDs in client-controlled parameters and implement proper authorization checks on deletion requests.
Description
better-auth passkey versions before 1.4.0 contain an insecure direct object reference vulnerability in the passkey deletion endpoint that allows authenticated users to delete arbitrary passkeys by ID. Attackers with valid sessions can submit crafted requests to the delete-passkey endpoint with enumerated passkey IDs to remove other users' passkeys.