CVE-2026-134313: better-auth kysely-adapter · Race Condition
Affects better-auth kysely-adapterSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 1.7.16 soon.
Data as of 21 Nov 2026, 17:15 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.6 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.8 |
- Patch
- Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade kysely-adapter and drizzle-adapter and better-auth to 1.7.16; kysely-adapter and drizzle-adapter and better-auth to 1.8.0-beta.5; kysely-adapter and drizzle-adapter and better-auth to 1.8.0-beta.5 or 1.7.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| better-authkysely-adapter | Affected
| Fixed in
|
| better-authkysely-adapter | Affected
| Fixed in
|
| better-authdrizzle-adapter | Affected
| Fixed in
|
| better-authdrizzle-adapter | Affected
| Fixed in
|
| better-authbetter-auth | Affected
| Fixed in
|
| better-authbetter-auth | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Better Auth versions 1.7.16 and 1.8.0-beta.5. Users should upgrade to these versions or later to remediate the vulnerability.
Description
Better Auth's kysely-adapter and drizzle-adapter versions before 1.7.16 and 1.8.0-beta.5 contain a race condition vulnerability involving MySQL or MariaDB serial IDs. The issue arises because the inserted row's ID is retrieved via a separate LAST_INSERT_ID() query that may execute on a different pooled connection. Under concurrent load, this can cause a user signing in to receive another user's session, allowing session hijacking.