Authentication persistence via omitted session deletion
Published Aug 1, 2026 · Updated Aug 1, 2026
Insufficient session expiration in Better Auth before 1.6.11 allows remote authenticated users to retain access after account deletion. Admin, anonymous, and SCIM deletion paths call deleteUser without first calling deleteSessions, leaving cached session payloads valid. Exposure requires secondaryStorage with storeSessionInDatabase false; an existing token retains its prior read and write access until its TTL expires.
Summary
What happened
Insufficient session expiration in Better Auth before 1.6.11 allows remote authenticated users to retain access after account deletion. Admin, anonymous, and SCIM deletion paths call deleteUser without first calling deleteSessions, leaving cached session payloads valid. Exposure requires secondaryStorage with storeSessionInDatabase false; an existing token retains its prior read and write access until its TTL expires.
The record
- CVE
- CVE-2026-67334
- Published
- Aug 1, 2026
- Updated
- Aug 1, 2026
- Vendor
- Better Auth
- Product
- Better Auth
- Classifications
- CWE-459, CWE-613, CWE-672, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 1, 2026CVE publishedPublication date reported by the CVE source.
- Aug 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.3.4 <1.6.11
- Affected versionversion=1.6.0 <1.6.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo