Brute Force Affecting @better-auth/drizzle-adapter package, versions >=1.6.17 <1.7.7
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-BETTERAUTHDRIZZLEADAPTER-21181301
- published18 Oct 2026
- disclosed15 Oct 2026
- creditMichał Ordon
Introduced: 15 Oct 2026
NewCVE-2026-110861 (opens in a new tab)How to fix?
Upgrade @better-auth/drizzle-adapter to version 1.7.7 or higher.
Overview
@better-auth/drizzle-adapter is a Drizzle adapter for Better Auth
Affected versions of this package are vulnerable to Brute Force via a race condition in the compare-and-swap UPDATE path in drizzle-adapter.ts and relations-v2/index.ts. Under PostgreSQL's READ COMMITTED isolation, the WHERE guard used to identify the target row was placed only in a subquery (id IN (targetIds)), which PostgreSQL does not re-evaluate after waiting on a concurrent writer. As a result, multiple concurrent UPDATE operations can all succeed once the first writer commits, allowing a second (or later) writer to overwrite a row even when the original guard condition is no longer satisfied. An attacker who can issue concurrent write requests can exploit this window to corrupt or overwrite record state they should not be able to modify.