@better-auth/drizzle-adapter
Affected
- introduced
1.6.17, fixed1.7.7(semver)
Fixed versions
1.7.7
Fix
- Fixed version
1.7.7npm install @better-auth/[email protected]
Advisory
Also known as: CVE-2026-110861
@better-auth/drizzle-adapter: Concurrent requests can exceed rate limits on PostgreSQL
Am I affected?
You are affected if you use @better-auth/drizzle-adapter from 1.6.17 through versions before 1.7.7 (including the 1.7.0 prereleases from beta.6 through rc.6) or @better-auth/kysely-adapter 1.6.17 through 1.6.31, and keep rate-limit records in a PostgreSQL database.
All of these must be true:
You are not affected if you store rate-limit records in memory (the default) or in secondary storage.
Summary
Database-backed rate limiting on PostgreSQL can let a burst of concurrent requests go over the configured maximum. When many requests arrive at the same time, several of them can pass the limit check together. This weakens the rate limit on password sign-in, two-factor verification, one-time codes, password resets, and other rate-limited endpoints.
Impact
An attacker who sends many requests at once can make more attempts than the application allows.
The issue does not bypass password or one-time-code validation. It does not directly compromise an account. The number of extra attempts is limited by the number of concurrent database connections, the number of application instances, and the rate-limit window.
Patches
@better-auth/kysely-adapter is fixed in 1.7.0. Upgrade to 1.7.0 or later.
The Drizzle fix is merged for the planned @better-auth/drizzle-adapter 1.7.7 release. That package is not available yet. Upgrade better-auth and the installed Drizzle adapter together when 1.7.7 is available. No database schema or public API migration is required.
Workarounds
In-memory storage also avoids this issue. However, each application instance keeps its own counter, so it may not enforce one shared limit in multi-instance or serverless deployments.
Low Basis: The source's own band: LOW
1.6.17, fixed 1.7.7 (semver)1.7.7
1.7.7npm install @better-auth/[email protected]1.6.17, fixed 1.7.0 (semver)1.7.0
1.7.0npm install @better-auth/[email protected]1.6.17, fixed 1.7.7 (semver)1.7.7
1.7.7npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0