CVE-2025-71399: Better Auth relies on better-call, which uses the rou3 router library
Affects better-authSource GCVE Database
Not known to be exploited · CVSS 8.6 High : upgrade to 1.4.5 soon.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade better-auth/better-auth to 1.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubbetter-auth/better-authpkg:github/better-auth/better-authOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Better Auth to version 1.4.5 or later, which includes the fixed rou3 router library. If upgrading is not immediately possible, ensure that the deployment environment (proxy or platform) normalizes URLs by collapsing multiple slashes to mitigate the issue. Patch status is not explicitly stated beyond the fixed version 1.4.5; check vendor advisories for the latest remediation guidance.
Description
Better Auth versions prior to 1.4.5 rely on the rou3 router library, which normalizes URL paths by removing empty segments. This behavior causes different URL paths with extra slashes (e.g., /path, //path, ///path) to resolve to the same route. As a result, attackers can bypass disabledPaths configuration and path-based rate limits by submitting requests with extra slashes in the URL. This vulnerability does not affect deployments where the proxy or platform normalizes URLs by collapsing multiple slashes. The issue is fixed in Better Auth version 1.4.5, which bundles the fixed rou3 library.
References
- github.com/better-auth/better-auth/security/advisories/GHSA-x732-6j76-qmhm (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2025-71399 (opens in a new tab)
- github.com/better-auth/better-auth/commit/f60b43fa648399534507c9ac7db36d705b8874c3 (opens in a new tab)
- vulncheck.com/advisories/better-auth-before-path-normalization-bypass-via-rou3 (opens in a new tab)