Skip to main content
CVE-2026-134321VulnerabilityPublished

better-auth from 0.8.1-beta.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and @better-auth/passkey from 1.6.25

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-134321· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 1.7.16 when convenient.

Data as of 21 Nov 2026, 19:45 UTC

CVSS 4.0 base score
2.3Low
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.02.3
CNA (VulnCheck)CVSS 3.14.2
Patch
Available – fixed in 1.7.16, 1.8.0-beta.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:L/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 better-auth to 1.7.16; better-auth to 1.8.0-beta.5; better-auth to 1.8.0-beta.5 or 1.7.16.

Affected software

ProductAffectedFixed in
better-authbetter-authAffected
  • >=0.8.1-beta.5 <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
better-authbetter-authAffected
  • >=1.6.25 <1.7.16
Fixed in
  • 1.7.16
npmbetter-authpkg:npm/better-authOther threatsAffected
  • >=0.8.1-beta.5 <1.7.16
  • >=1.8.0-beta.0 <1.8.0-beta.5
  • >=1.6.25 <1.7.16
Fixed in
  • 1.7.16
  • 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, organizations should consider limiting session lifetimes, monitoring for unusual session activity, and applying any vendor-recommended temporary mitigations if published.

Description

A vulnerability in better-auth and @better-auth/passkey allows revoked sessions to remain valid due to non-atomic updates of secondary storage session lists and reliance on cookie-cached sessions. This flaw enables an attacker with a valid session to bypass bulk revocation or bans, or to use a revoked cached session to register a passkey or create a persistent session.

References

Community reviews

Loading reviews…