[GHSA-4vcf-q4xf-f48m] Better Auth Passkey plugin allows deletion of arbitrary passkeys by ID - #8944
Open
FROWNINGdev wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
FROWNINGdev/advisory-improvement-8944
August 2, 2026 17:25
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Add
CVE-2025-71400as an alias for this advisory.The unreviewed record GHSA-44ff-3cmc-mgqf describes the same vulnerability — an insecure direct object reference in the passkey deletion endpoint that lets an authenticated user delete other users' passkeys by enumerating IDs, fixed in 1.4.0 — and lists this advisory as its first reference. The two records are duplicates of a single issue, split across keys: this one carries the package mapping (
npm:@better-auth/passkey,< 1.4.0) but no CVE ID, while the unreviewed record carriesCVE-2025-71400but no affected package or version data. Consumers matching on the CVE therefore miss the affected-version range, and consumers matching on the npm package miss the CVE.This change is limited to the
aliasesfield; no other fields are touched.References