@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:
- Rate limiting is enabled.
- Rate-limit records are stored in the database.
- The database is PostgreSQL, used through one of the adapter versions above.
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
- Store rate-limit records in secondary storage.
- Use a custom rate-limit storage that checks and increments the counter in one atomic step. An atomic step cannot be interrupted by another request.
- Enforce the intended limit at an upstream layer, such as a reverse proxy or gateway.
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.
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
Verweise
- https://github.com/better-auth/better-auth/security/advisories/GHSA-44jh-23m7-hpcf
- https://github.com/better-auth/better-auth/pull/11331
- https://github.com/better-auth/better-auth/commit/35d7cd389220f99cfc98ac699e6a42b48313a740
- https://github.com/better-auth/better-auth
- https://github.com/better-auth/better-auth/releases/tag/v1.7.7
- CVSS-Vektor
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N- Schwäche (CWE)
CWE-307, CWE-362- Plattform
- npm
- Paket
better-auth, @better-auth/drizzle-adapter, @better-auth/kysely-adapter- Veröffentlicht
- 27.10.2026
- Aktualisiert
- 27.10.2026 17:17
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-44jh-23m7-hpcf - CC BY 4.0
Schwachstellenhistorie: better-auth
Alle veröffentlichten Schwachstellen dieses Pakets (npm-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 26
- Erste → letzte
- 12.2024 10.2026
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 0
Verteilung nach Schweregrad
- Kritisch 3
- Hoch 16
- Mittel 3
- Niedrig 4
Veröffentlichungen pro Jahr
- 2024: 1
- 2025: 8
- 2026: 17
-
@better-auth/drizzle-adapter: Concurrent requests can exceed rate limits on PostgreSQL dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.