Skip to main content
Menu
CVEs

Better Auth Kysely Adapter session mix-up via race in MySQL insert ID lookup

Affects Better Auth setups on MySQL or MariaDB that set advanced.database.generateId to "serial" and use the default Kysely adapter or the Drizzle adapter with a connection pool. Fixed in 1.7.16 and 1.8.0-beta.5.

CVE-2026-134313Published November 21, 2026, updated

7.6HighCNA
Exploited
No known exploitation
Fix
Fixed in 1.7.16, 1.8.0-beta.5
Who is exposed
Specific setups only

Summary

Written by a model

Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition with MySQL or MariaDB serial IDs because the inserted row's ID is read via a separate LAST_INSERT_ID() query that may run on a different pooled connection. Under concurrent load, a user signing in can receive another user's session and act as that user.

Who should check

Teams running better-auth, @better-auth/kysely-adapter or @better-auth/drizzle-adapter on MySQL or MariaDB with generateId serial and a connection pool.

Not fixed by: A single-connection pool does not prevent this.

“Your database is MySQL or MariaDB.”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    Database is MySQL or MariaDB. advanced.database.generateId is set to "serial". Uses the default Kysely adapter or the Drizzle adapter with a connection pool.
  2. Upgrade to a fixed version: 1.7.16, 1.8.0-beta.5.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-134313 (Better Auth before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 Session Mix-Up via MySQL Serial IDs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-134313 (entry last updated 2026-11-21):
Affected:
- npm package @better-auth/kysely-adapter: from 1.5.0-beta.9, fixed in 1.7.16
- npm package @better-auth/kysely-adapter: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
- npm package @better-auth/drizzle-adapter: from 1.5.0-beta.9, fixed in 1.7.16
- npm package @better-auth/drizzle-adapter: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
- npm package better-auth: fixed in 1.7.16
- npm package better-auth: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
Fixed versions: 1.7.16, 1.8.0-beta.5.
Conditions (all must be true for the bug to be hit):
- Database is MySQL or MariaDB. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-48c2-w96j-mv3m)
- advanced.database.generateId is set to "serial". (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-48c2-w96j-mv3m)
- Uses the default Kysely adapter or the Drizzle adapter with a connection pool. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-48c2-w96j-mv3m)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134313 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134313 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/better-auth/better-auth/security/advisories/GHSA-48c2-w96j-mv3m
- https://www.vulncheck.com/advisories/better-auth-before-1.7.16-and-1.8.0-beta.0-before-1.8.0-beta.5-session-mix-up-via-mysql-serial-ids
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-134313
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134313"}.

Affected versions

cve.now Index

36Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach20/20better-auth: 19.7M downloads a week
  • Severity7.6/10CVSS 7.6
  • No patch0/5No signal

What would change the score

  • Would score about 86 if added to CISA KEV
  • Would score about 81 if CISA's SSVC rates exploitation active
  • Would score about 43 if CISA's SSVC rates it automatable

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · better-auth/better-auth · Advisory GHSA-48c2-w96j-mv3m
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-134313
RecordNVD · CVE-2026-134313
Other links 1
Linkvulncheck.com · advisories/better-auth-before-1.7.16-and-1.8.0-beta.0-before-1.8.0-beta.5-session-mix-up-via-mysql-serial-ids

Questions about CVE-2026-134313

Is CVE-2026-134313 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A user who signs in can receive another user's session and act as that user. A sign-up can also return another user's record.

Source: github.com

Which versions are affected by CVE-2026-134313?

@better-auth/kysely-adapter (npm): from 1.5.0-beta.9 before 1.7.16. @better-auth/kysely-adapter (npm): from 1.8.0-beta.0 before 1.8.0-beta.5. @better-auth/drizzle-adapter (npm): from 1.5.0-beta.9 before 1.7.16. @better-auth/drizzle-adapter (npm): from 1.8.0-beta.0 before 1.8.0-beta.5. better-auth (npm): before 1.7.16. 1 more package is listed on the page.

Source: cve.now feed data

Am I affected, and how do I check?

The issue needs three conditions together: a MySQL or MariaDB database, advanced.database.generateId set to "serial", and either the default Kysely adapter or the Drizzle adapter with a connection pool. The affected versions are better-auth and the kysely-adapter and drizzle-adapter packages from 1.5.0-beta.9 to before 1.7.16, and from 1.8.0-beta.0 to before 1.8.0-beta.5. To check, look at the database type and the advanced.database.generateId value in the Better Auth configuration, and at the installed better-auth and adapter package versions.

Source: github.com

How do I fix CVE-2026-134313?

Upgrade better-auth and the kysely-adapter or drizzle-adapter packages to 1.7.16 or to 1.8.0-beta.5.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.