better-auth passkey before 1.4.0 IDOR via delete-passkey

published 2025-11-25 11 mo ago modified 2026-10-08 31 d ago also EUVD-2025-210591 , GHSA-4vcf-q4xf-f48m

cvss: 7.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits: 0; none known

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.

Patch / fix

fixed in 2 links 1

npm @better-auth/passkey 1.4.0
better-auth passkey 1.4.0

github.com/better-auth/better-auth@06d6823 commit

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 3 mo ago (2026-08-03)

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	7.1	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
CNA	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
GitHub	3.1	7.1	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
CNA	4.0	7.1	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem	package	affected	fixed in
npm	@better-auth/passkey	<1.4.0	1.4.0

Affected products

better-auth passkey

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key
CWE-284 Improper Access Control

References

github.com /better-auth/better-auth/commit/06d68239e
web
github.com /better-auth/better-auth/security/advisories/GHSA-4vcf-q4xf-f48m
vendor-advisory, web
vulncheck.com /advisories/better-auth-passkey-before-idor-via-delete-passkey
third-party-advisory
github.com /better-auth/better-auth
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary