better-auth versions before 1.6.11 fail to delete cached sessions when removing users via admin, anonymous, or SCIM endpoints when secondaryStorage… (CVE-2026-67334)
better-auth versions before 1.6.11 have a vulnerability where cached user sessions are not deleted when users are removed via admin, anonymous, or SCIM endpoints if secondaryStorage is configured and storeSessionInDatabase is false. This allows attackers to reuse deleted user session tokens to maintain authentication for up to seven days after the account deletion. The issue has a medium severity with a CVSS score of 3.8.
AI Analysis
Technical Summary
The vulnerability in better-auth prior to version 1.6.11 involves failure to delete cached sessions upon user removal through various endpoints when secondaryStorage is enabled and storeSessionInDatabase is disabled. This session persistence flaw (CWE-459) enables attackers to reuse session tokens of deleted users, maintaining authenticated access for up to seven days post-deletion. The CVSS 3.1 vector indicates network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and limited confidentiality and integrity impact.
Potential Impact
Attackers with high privileges can exploit this vulnerability to reuse session tokens of deleted users, maintaining unauthorized authenticated access for up to seven days after the user account has been deleted. The confidentiality and integrity of the system are impacted to a limited extent, while availability is not affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should consider manually invalidating cached sessions when deleting users, especially when using secondaryStorage with storeSessionInDatabase set to false. Monitor vendor channels for updates and apply patches promptly once released.
better-auth versions before 1.6.11 fail to delete cached sessions when removing users via admin, anonymous, or SCIM endpoints when secondaryStorage… (CVE-2026-67334)
Description
better-auth versions before 1.6.11 have a vulnerability where cached user sessions are not deleted when users are removed via admin, anonymous, or SCIM endpoints if secondaryStorage is configured and storeSessionInDatabase is false. This allows attackers to reuse deleted user session tokens to maintain authentication for up to seven days after the account deletion. The issue has a medium severity with a CVSS score of 3.8.
CVSS v3.1
Score 3.8low
Affected software
pkg:github/better-auth/better-authRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in better-auth prior to version 1.6.11 involves failure to delete cached sessions upon user removal through various endpoints when secondaryStorage is enabled and storeSessionInDatabase is disabled. This session persistence flaw (CWE-459) enables attackers to reuse session tokens of deleted users, maintaining authenticated access for up to seven days post-deletion. The CVSS 3.1 vector indicates network attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and limited confidentiality and integrity impact.
Potential Impact
Attackers with high privileges can exploit this vulnerability to reuse session tokens of deleted users, maintaining unauthorized authenticated access for up to seven days after the user account has been deleted. The confidentiality and integrity of the system are impacted to a limited extent, while availability is not affected.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, administrators should consider manually invalidating cached sessions when deleting users, especially when using secondaryStorage with storeSessionInDatabase set to false. Monitor vendor channels for updates and apply patches promptly once released.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-gj53-4jmf-7745
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-67334"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a6e6291bf32cb7a344f5eea
Added to database: 08/01/2026, 21:18:09 UTC
Last enriched: 08/01/2026, 21:20:11 UTC
Last updated: 08/01/2026, 22:37:50 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.