CVE-2026-134321
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 before 1.7.16 and 1.8.0-beta.0 before 1.
Impact
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 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, let revoked sessions stay valid because secondary storage session lists are updated non-atomically and some routes trust cookie-cached sessions. An attacker holding a valid session can evade bulk revocation or bans, or use a revoked cached session to register a passkey or create a lasting session.
An attacker can exploit this over the network, without logging in, but a user has to do something, such as open a file or a link. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read, low risk of data or systems being changed.
Affected products · Better-auth
| Product | Affected versions |
|---|---|
| Better-auth | from 0.8.1-beta.5 before 1.7.16 from 1.8.0-beta.0 before 1.8.0-beta.5 from 1.6.25 before 1.7.16 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/better-auth/better-auth/security/advisories/GHSA-fvxx-76fc-893x
- https://www.vulncheck.com/advisories/better-auth-before-1.7.16-session-revocation-bypass-via-secondary-storage-and-cookie-cache
- https://github.com/advisories/GHSA-hrqw-cfx5-6fr3
- https://nvd.nist.gov/vuln/detail/CVE-2026-134321