better-auth Stale Sessions Persist After User Deletion
better-auth
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| better-auth npm |
|
|
| @better-auth/scim npm |
|
|
better-auth
| Product | Affected | Fixed in |
|---|---|---|
| better-auth npm |
|
|
| @better-auth/scim npm |
|
|
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.
From the CVE record · VulnCheck
When secondaryStorage is configured and storeSessionInDatabase is false, better-auth fails to delete cached sessions when users are removed through admin, anonymous, or SCIM endpoints. An attacker with a deleted user's session token can remain authenticated for up to seven days after account deletion.
Check deployments using npm better-auth versions >=0.3.4 <1.6.11 or npm @better-auth/scim versions >=1.6.0 <1.6.11.