[GHSA-569q-mpph-wgww] Better Auth affected by external request basePath modification DoS - #8943
Open
FROWNINGdev wants to merge 2 commits into
Conversation
github-actions
Bot
changed the base branch from
main
to
FROWNINGdev/advisory-improvement-8943
August 2, 2026 17:19
The previous submission for this advisory (github#8942) was still open when this PR was created, so the check failed with "You already have a pending improvement for this advisory". github#8942 is now closed; this empty commit re-triggers the check. No file changes.
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-71401as an alias for this advisory.The unreviewed record GHSA-3q45-2fh7-66cj describes the same vulnerability — better-auth allowing an external request to configure
baseURLwhen it is not otherwise defined, poisoning the router base path and causing all routes to 404, fixed in 1.4.2 — 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,< 1.4.2) but no CVE ID, while the unreviewed record carriesCVE-2025-71401but 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
Note
This supersedes #8942, which I submitted through the web improvement form. That form rejected the stored CVSS 4.0 vector because it ends with the Threat metric
/E:P, and the resulting submission unintentionally dropped that suffix and bumped the severity from LOW to MODERATE — neither of which I intended. I am closing #8942 in favour of this PR, which contains only the alias change.