Skip to main content
CVE-2026-134313VulnerabilityPublished

Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134313· High 7.6

Not known to be exploited · CVSS 7.6 High : upgrade to 1.7.16 soon.

Data as of 21 Nov 2026, 19:58 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.07.6
CNA (VulnCheck)CVSS 3.16.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 21 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

ProductAffectedFixed in
better-authkysely-adapterAffected
  • >=1.5.0-beta.9 <1.7.16
Fixed in
  • 1.7.16
better-authkysely-adapterAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5
better-authdrizzle-adapterAffected
  • >=1.5.0-beta.9 <1.7.16
Fixed in
  • 1.7.16
better-authdrizzle-adapterAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5
better-authbetter-authAffected
  • <1.7.16
Fixed in
  • 1.7.16
better-authbetter-authAffected
  • >=1.8.0-beta.0 <1.8.0-beta.5
Fixed in
  • 1.8.0-beta.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider reducing concurrent sign-in load or modifying connection pooling behavior to ensure LAST_INSERT_ID() queries run on the same connection as the insert operation.

Description

Better Auth versions before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 have a race condition vulnerability involving MySQL or MariaDB serial IDs. The issue arises because the inserted row's ID is retrieved using 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.

References

Community reviews

Loading reviews…