GHSA-44jh-23m7-hpcf: @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.
Published Oct 27, 2026
Affected packages
@better-auth/drizzle-adapter
- Ecosystem
- npm
- Affected
- >= 1.6.17, < 1.7.7
- Fixed in
- 1.7.7
- Check
npm ls @better-auth/drizzle-adapter
@better-auth/kysely-adapter
- Ecosystem
- npm
- Affected
- >= 1.6.17, < 1.7.0
- Fixed in
- 1.7.0
- Check
npm ls @better-auth/kysely-adapter
better-auth
- Ecosystem
- npm
- Affected
- >= 1.6.17, < 1.7.7
- Fixed in
- 1.7.7
- Check
npm ls better-auth
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to designorant.
References
- 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/releases/tag/v1.7.7
- https://github.com/advisories/GHSA-44jh-23m7-hpcf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-114607
better-auth: OAuth state can be used as a Magic Link to sign in as another user
critical9.1Oct 27, 2026GHSA-q84f-53jg-9ppm
better-auth: Device login approval does not show the requesting client or permissions
high8.1Oct 27, 2026GHSA-r4xp-prcw-77qf
better-auth: OAuth Proxy lets an attacker sign in as another user
high7.4Oct 27, 2026GHSA-qq9h-g4jm-xgf3
Better Auth: Account takeover via pre-account hijacking on magic-link and email-OTP sign-in
high8.3Jul 24, 2026CVE-2026-53512
Better Auth: OAuth refresh-token replay via missing client authentication on oidc-provider and mcp plugins
critical9.1Jul 7, 2026CVE-2026-53514
Better Auth vulnerable to unauthorized invitation acceptance via unverified email match in organization plugin
high7.7Jul 7, 2026
