better-auth Stale Sessions Persist After User Deletion

published 2026-07-07 4 mo ago modified 2026-10-08 31 d ago also GHSA-2vg6-77g8-24mp , EUVD-2026-51828

cvss: 3.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits: 0; none known

better-auth versions before 1.6.11 fail to delete cached sessions when removing users via admin, anonymous, or SCIM endpoints when secondaryStorage is configured and storeSessionInDatabase is false. Attackers can reuse deleted user session tokens to maintain authentication for up to seven days after account deletion.

Patch / fix

fixed in 3 links 1

npm better-auth 1.6.11
npm @better-auth/scim 1.6.11
better-auth better-auth 1.6.11

github.com/better-auth/better-auth/releases/tag/v1.6.11 release

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: partial
Assessed: 3 mo ago (2026-08-03)

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	4.0	5.1	CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CNA	3.1	3.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
CNA	4.0	5.1	CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
GitHub	3.1	3.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	better-auth	>=0.3.4, <1.6.11	1.6.11
npm	@better-auth/scim	>=1.6.0, <1.6.11	1.6.11

Affected products

better-auth better-auth

Classification

Weakness

CWE-459 Incomplete Cleanup
CWE-613 DEPRECATED: Insufficient Session Expiration
CWE-672 Operation on a Resource after Expiration or Release

References

github.com /better-auth/better-auth/security/advisories/GHSA-2vg6-77g8-24mp
vendor-advisory, web
vulncheck.com /advisories/better-auth-stale-sessions-persist-after-user-deletion
third-party-advisory
github.com /better-auth/better-auth
package
github.com /better-auth/better-auth/releases/tag/v1.6.11
web

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary