Description
Better Auth relies on better-call, which uses the rou3 router library. In affected versions of rou3, paths are normalized by removing empty segments, so /path, //path, and ///path resolve to the same route. In Better Auth versions prior to 1.4.5 (which bundles the fixed rou3), this can allow attackers to bypass disabledPaths configuration and path-based rate limits by submitting requests with extra slashes in the URL path. The issue does not apply in deployments where the proxy or platform normalizes URLs by collapsing multiple slashes.
Published: 2026-08-02
Score: 8.8 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Better Auth relies on the rou3 router library, and older versions of rou3 normalize URLs by stripping empty segments. An attacker can send requests that include extra slashes in the path, such as /path, //path, or ///path. Because Better Auth versions prior to 1.4.5 perform no additional validation, these crafted URLs bypass the disabledPaths configuration and any path‑based rate limits that are meant to throttle or block traffic. This vulnerability is a classic input validation failure (CWE‑20) and enables an attacker to compromise critical traffic‑control mechanisms without authentication.

Affected Systems

The affected product is Better Auth, the OAuth provider application. All releases before version 1.4.5 are impacted, including 1.4.4 and older branches. No specific minor versions were enumerated beyond the major revision number.

Risk and Exploitability

The CVSS score of 8.8 places the vulnerability in the high severity range, and the EPSS score is not available. The vulnerability is not listed in the CISA KEV catalog. Exploitation is remote over HTTP and does not require credentials; an attacker can craft a single URL with extra slashes to trigger the bypass. If the deployment does not perform its own URL normalization—such as by a reverse proxy or platform component—this weakness is directly exploitable and can lead to denial of service or further bypass of security controls.

Generated by OpenCVE AI on August 3, 2026 at 09:17 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Better Auth to version 1.4.5 or later, which includes a patched rou3 library
  • Configure an upstream proxy or platform component to collapse multiple slashes before the request reaches Better Auth if an immediate upgrade is not possible
  • Enforce disabled paths and rate limits at the network or proxy layer instead of relying solely on the application’s configuration to avoid similar normalization bypasses

Generated by OpenCVE AI on August 3, 2026 at 09:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 03 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 03 Aug 2026 11:30:00 +0000

Type Values Removed Values Added
Title Better Auth before 1.4.4 Path Normalization Bypass via rou3 Better Auth before 1.4.5 Path Normalization Bypass via rou3

Sun, 02 Aug 2026 15:15:00 +0000

Type Values Removed Values Added
First Time appeared Better-auth better Auth
Vendors & Products Better-auth better Auth

Sun, 02 Aug 2026 12:45:00 +0000

Type Values Removed Values Added
Description Better Auth relies on better-call, which uses the rou3 router library. In affected versions of rou3, paths are normalized by removing empty segments, so /path, //path, and ///path resolve to the same route. In Better Auth versions prior to 1.4.5 (which bundles the fixed rou3), this can allow attackers to bypass disabledPaths configuration and path-based rate limits by submitting requests with extra slashes in the URL path. The issue does not apply in deployments where the proxy or platform normalizes URLs by collapsing multiple slashes.
Title Better Auth before 1.4.4 Path Normalization Bypass via rou3
First Time appeared Better-auth
Better-auth better-auth\/oauth-provider
Weaknesses CWE-20
CPEs cpe:2.3:a:better-auth:better-auth\/oauth-provider:*:*:*:*:*:node.js:*:*
Vendors & Products Better-auth
Better-auth better-auth\/oauth-provider
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H'}

cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Better-auth Better-auth\/oauth-provider Better Auth
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-03T15:50:52.728Z

Reserved: 2026-07-18T12:38:41.077Z

Link: CVE-2025-71399

cve-icon Vulnrichment

Updated: 2026-08-03T15:50:47.129Z

cve-icon NVD

Status : Received

Published: 2026-08-02T13:16:52.210

Modified: 2026-08-03T17:16:28.867

Link: CVE-2025-71399

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-03T09:30:17Z

Weaknesses
  • CWE-20

    Improper Input Validation