Better Auth session revocation bypass in secondary storage
Affects better-auth with secondaryStorage from 0.8.1-beta.5, or session.cookieCache with passkey, device authorization or passwordless 2FA enrollment from 1.6.25. Fixed in 1.7.16 and 1.8.0-beta.5.
- 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 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.
Who should check
Teams running better-auth with secondaryStorage or session.cookieCache, and teams using @better-auth/passkey for passkey registration, device authorization or passwordless two-factor enrollment.
“You are affected if you use better-auth with any of these:”
What to do
Check whether your setup matches what the bug needs.
Uses secondaryStorage, from 0.8.1-beta.5. Uses session.cookieCache with passkey registration, device authorization, or passwordless two-factor enrollment, from 1.6.25.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-134321 (better-auth before 1.7.16 Session Revocation Bypass via Secondary Storage and Cookie Cache), 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-134321 (entry last updated 2026-11-21):
Affected:
- npm package better-auth: from 0.8.1-beta.5, fixed in 1.7.16
- npm package better-auth: from 1.8.0-beta.0, fixed in 1.8.0-beta.5
- npm package @better-auth/passkey: from 1.6.25, fixed in 1.7.16
- npm package @better-auth/passkey: 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):
- Uses secondaryStorage, from 0.8.1-beta.5. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-fvxx-76fc-893x)
- Uses session.cookieCache with passkey registration, device authorization, or passwordless two-factor enrollment, from 1.6.25. (source: https://github.com/better-auth/better-auth/security/advisories/GHSA-fvxx-76fc-893x)
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, no login, a user action.
CISA KEV: CVE-2026-134321 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134321 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-fvxx-76fc-893x
- https://www.vulncheck.com/advisories/better-auth-before-1.7.16-session-revocation-bypass-via-secondary-storage-and-cookie-cache
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-134321
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-134321"}.Affected versions
- better-authFrom 0.8.1-beta.5 · fixed in 1.7.16Fixed in 1.7.16 (released Nov 3, 2026, 18 days before disclosure).
- better-authFrom 1.8.0-beta.0 · fixed in 1.8.0-beta.5Fixed in 1.8.0-beta.5 (released Nov 3, 2026, 18 days before disclosure).The latest release, 1.7.26, is not affected.
- @better-auth/passkeyFrom 1.6.25 · fixed in 1.7.16Fixed in 1.7.16 (released Nov 3, 2026, 18 days before disclosure).
- @better-auth/passkeyFrom 1.8.0-beta.0 · fixed in 1.8.0-beta.5Fixed in 1.8.0-beta.5 (released Nov 3, 2026, 18 days before disclosure).The latest release, 1.7.25, is not affected.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach20/20better-auth: 19.7M downloads a week
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 84 if added to CISA KEV
- Would score about 79 if CISA's SSVC rates exploitation active
Impact
- Widely usedbetter-auth has 19.7m weekly downloads. npmjs.com
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · better-auth/better-auth · Advisory GHSA-fvxx-76fc-893x |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134321 |
| Record | NVD · CVE-2026-134321 |
| Other links 1 | |
| Link | vulncheck.com · advisories/better-auth-before-1.7.16-session-revocation-bypass-via-secondary-storage-and-cookie-cache |
Questions about CVE-2026-134321
Is CVE-2026-134321 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 session that has been revoked can still grant access in some cases. This lets an attacker who holds a valid session keep access despite bulk revocation or bans, and create a passkey or a lasting session from a revoked cached session.
Source: github.com
Which versions are affected by CVE-2026-134321?
better-auth (npm): from 0.8.1-beta.5 before 1.7.16. better-auth (npm): from 1.8.0-beta.0 before 1.8.0-beta.5. @better-auth/passkey (npm): from 1.6.25 before 1.7.16. @better-auth/passkey (npm): from 1.8.0-beta.0 before 1.8.0-beta.5.
Source: cve.now feed data
Am I affected, and how do I check?
Versions from 0.8.1-beta.5 that use secondaryStorage are affected, and so are versions from 1.6.25 that use session.cookieCache with passkey registration, device authorization, or passwordless two-factor enrollment. To check a setup, look at the installed better-auth package version and whether secondaryStorage or session.cookieCache is configured.
Source: github.com
How do I fix CVE-2026-134321?
Upgrade to better-auth 1.7.16 or later on the 1.7 line, or to 1.8.0-beta.5 or later on the 1.8 beta line.
Source: github.com
Related
- CVE-2026-67336better-auth before 1.6.11 Insecure Cryptographic Defaults via oidcProvider
- CVE-2026-110862Better Auth 1.4.0-beta.18 before 1.7.7 Authentication Bypass via Magic Link
- CVE-2025-71401better-auth before 1.4.2 basePath Modification DoS
- CVE-2026-114607better-auth: OAuth state can be used as a Magic Link to sign in as another user
- CVE-2026-110864Better Auth 1.5.0-beta.12 before 1.7.7 Authentication Bypass via OAuth Proxy
- CVE-2025-71399Better Auth before 1.4.5 Path Normalization Bypass via rou3
No corrections so far. Something wrong on this page? Report an error.