🛡️ CVE-2025-71399 — better-auth

🟠 CVSS 8.6 — High ✅ No Known Exploit CWE-400 NVD
8.6
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Better Auth's rou3 Dependency has Double-Slash Path Normalization which can Bypass disabledPaths Config and Rate Limits

Summary

An issue in the underlying router library rou3 can cause /path and //path to be treated as identical routes. If your environment does not normalize incoming URLs (e.g., by collapsing multiple slashes), this can allow bypasses of disabledPaths and path-based rate limits.

Details

Better Auth uses better-call, which internally relies on rou3 for routing. Affected versions of rou3 normalize paths by removing empty segments. As a result:

  • /sign-in/email
  • //sign-in/email
  • ///sign-in/email

…all resolve to the same route.

Some production setups *automatically* collapse multiple slashes. This includes:

  • Vercel with Nextjs (default)
  • Cloudflare - when normalize to urls origin is enabled (https://developers.cloudflare.com/rules/normalization/settings/#normalize-urls-to-origin)

In these environments and other configurations where //path reach Better Auth as /path, the issue does not apply.

Fix

Updating rou3 to the latest version resolves the issue:

  • better-call previously depended on "rou3": "^0.5.1"
  • The fix was introduced after that version

(commit: [https://github.com/h3js/rou3/commit/f60b43fa648399534507c9ac7db36d705b8874c3](https://github.com/h3js/rou3/commit/f60b43fa648399534507c9ac7db36d705b8874c3))

Better Auth recommends:

1. Upgrading to Better Auth v1.4.5 or later, which includes the updated rou3.

2. Ensuring the proxy normalizes URLs.

3. If project maintainers cannot upgrade yet, they can protect their app by normalizing url before it reaches better-auth handler. See example below:

```ts

const req = new Request(...) // this would be the actual request object

const url = new URL(req.url);

const normalizedPath = url.pathname.replace(/\/+/g, "/");

if (url.pathname !== normalizedPath) {

url.pathname = normalizedPath;

// Update the raw request pathname

Object.defineProperty(req, "url", {

value: url.toString(),

writable: true,

configurable: true,

});

}

```

Impact

  • Bypass disabledPaths
  • Bypass path-based rate limits

The impact of bypassing disabled paths could vary based on a project's configuration.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability high.

Weakness class

CVE-2025-71399 is classified as CWE-400: Uncontrolled Resource Consumption. A request can consume memory, CPU or storage without limit, exhausting capacity for everyone else.

Affected software

CVE-2025-71399 is recorded against 2 packages.

  • better-auth
  • unknown

Timeline and source

Published on 16 December 2025 and last revised on 3 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
github.com (Package)

Details

Severity HIGH
CVSS Score 8.6
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CWE CWE-400
Public Exploit ✅ No
Source NVD
Published 2025-12-16
Updated 2026-08-12
Modified 2026-08-03
Fix URL N/A

Affected Packages

Software From version Fixed in
better-auth
unknown

Similar Threats

Site Security Check

Is better-auth part of your stack?

CVE-2025-71399 is rated CVSS 8.6 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.