How severe is GHSA-4vcf-q4xf-f48m?

GHSA-4vcf-q4xf-f48m has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4vcf-q4xf-f48m?

GHSA-4vcf-q4xf-f48m affects the following packages: @better-auth/passkey (npm). Ecosystems affected: npm.

How do I fix GHSA-4vcf-q4xf-f48m?

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.

How do I detect GHSA-4vcf-q4xf-f48m in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @better-auth/passkey. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4vcf-q4xf-f48m if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-4vcf-q4xf-f48m?

O3 pinpoints whether GHSA-4vcf-q4xf-f48m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4vcf-q4xf-f48m actively exploited in the wild?

No public exploit code has been indexed for GHSA-4vcf-q4xf-f48m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-4vcf-q4xf-f48m?

GHSA-4vcf-q4xf-f48m is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4vcf-q4xf-f48m published, and has it been updated?

GHSA-4vcf-q4xf-f48m was published on November 25, 2025 and was last updated on August 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-4vcf-q4xf-f48m

HIGH

GHSA-4vcf-q4xf-f48m is a high-severity (CVSS 7.1) CWE-639 vulnerability in @better-auth/passkey. O3 Security confirms whether GHSA-4vcf-q4xf-f48m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Better Auth Passkey Plugin allows passkey deletion through IDOR

Also known asCVE-2025-71400

Published

Nov 25, 2025

Updated

Aug 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

📦@better-auth/passkey

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@better-auth/passkey`	all versions	1.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @better-auth/passkey. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-4vcf-q4xf-f48m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4vcf-q4xf-f48m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-4vcf-q4xf-f48m across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works