Vulnerability in @better-auth/passkey (CVE-2025-71400)
Summary
Vulnerability in @better-auth/passkey (CVE-2025-71400). Data can be tampered with by attackers. Exploitable via POST /passkey/delete-passkey. Mitigation: upgrade to 1.4.0 or later.
Original description
The description as published by the source.
Summary
Affected versions of the better-auth passkey plugin allow users with any valid session to delete arbitrary passkeys via their ID using POST /passkey/delete-passkey.
Details
ctx.body.id is implicitly trusted and used in passkey deletion queries.
better-auth applications configured with useNumberId may use auto incrementing IDs which makes it trivial to delete all passkeys via enumeration.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-71400 has been found in @better-auth/passkey.
Attackers can target a specific entry point like POST /passkey/delete-passkey over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @better-auth/passkey to 1.4.0 or later.
If unsure, ask your IT team or search "@better-auth/passkey CVE-2025-71400" on the vendor's site.
CVE-2025-71400 (@better-auth/passkey) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /passkey/delete-passkey / ctx.body.id / useNumberId
Patched: 1.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-639) exists in @better-auth/passkey. Attackers reach the vulnerable code path via POST /passkey/delete-passkey.
Check the vendor advisory for the affected versions of @better-auth/passkey. Attack surface: POST /passkey/delete-passkey / ctx.body.id / useNumberId.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 1.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /passkey/delete-passkey requests with malformed payloads or SQL meta-characters. Run grep -r '@better-auth/passkey' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@better-auth/passkey' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@better-auth/passkeyを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /passkey/delete-passkey' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /passkey/delete-passkeyへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade @better-auth/passkey to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /passkey/delete-passkey on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com
- web github.com