NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
HIGH severity

Better Auth Passkey Plugin allows passkey deletion through IDORGHSA-4vcf-q4xf-f48m

HIGHFix: better-auth/better-auth@06d6823

GHSA-4vcf-q4xf-f48m is a high-severity (CVSS 7.1) CWE-639 vulnerability in @better-auth/passkey. A fix is available for @better-auth/passkey — see the affected versions and patch details below.

Also known asCVE-2025-71400
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-4vcf-q4xf-f48m.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs29th percentile — riskier than 29% of all scored CVEsHighest risk
0.00%0.28%0.57%0.85%0.2%0.4%0.4%Sep 26Oct 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

91other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@better-auth/passkeynpm
2.8Mdownloads / week

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@better-auth/passkeyall versions1.4.0npm install @better-auth/passkey@1.4.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @better-auth/passkey, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @better-auth/passkey to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4vcf-q4xf-f48m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

# 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.
O3 Security · Impact-Aware SCA

Is GHSA-4vcf-q4xf-f48m in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Better Auth Passkey Plugin allows passkey deletion…