CVE-2026-44648: SillyTavern: Existing sessions are not invalidated after password change, allowing session reuse and account takeover
Summary Changing a user’s password does not invalidate existing sessions, allowing an attacker with a stolen cookie to retain access even after the victim resets their password. Details SillyTavern relies on cookie-session for authentication, storing all session data (user handle, permissions) in a signed cookie.
Published May 12, 2026 · Updated Jun 9, 2026
Affected packages
sillytavern
- Ecosystem
- npm
- Affected
- <= 1.17.0
- Fixed in
- 1.18.0
- Check
npm ls sillytavern
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Changing a user’s password does not invalidate existing sessions, allowing an attacker with a stolen cookie to retain access even after the victim resets their password.
Details
SillyTavern relies on cookie-session for authentication, storing all session data (user handle, permissions) in a signed cookie. The endpoints POST /api/users/change-password and POST /api/users/recover-step2 only update the password hash in the database but do not expire current sessions. Because the session is stateless and stored entirely in the client cookie, there is no server-side mechanism to revoke a token once issued.
PoC
1.Log into the same SillyTavern account from two different browsers (e.g., Chrome and Firefox private mode). 2.In Chrome, change the account password under User Settings → Change Password. 3.In Firefox, refresh the page or perform a protected action (e.g., view API keys). 4.Expected: Firefox session should be invalidated and ask for login. 5.Actual: Firefox remains fully authenticated, able to perform all actions as the targeted user.
Impact
An attacker who obtains a valid session cookie (via XSS, MITM, physical access, etc.) can continue using it indefinitely, even after the legitimate user changes their password. This nullifies the most common recovery measure against session theft. The default cookie lifespan is 400 days, giving an attacker a very long exploitation window.
Resolution
A fix was released in the version 1.18.0, invalidating a session cookie on account password change.
Credited to zzzm0919.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-46372
SillyTavern: SSRF in SearXNG Search Proxy via Unvalidated baseUrl
high8.5May 19, 2026CVE-2026-44649
SillyTavern has Authentication Bypass via SSO Header Injection
critical9.8May 12, 2026CVE-2026-44650
SillyTavern has a Path Traversal issue
critical9.1May 12, 2026CVE-2026-44651
SillyTavern has a reflected XSS vulnerability in the CORS proxy middleware
medium6.9May 12, 2026CVE-2026-44652
SillyTavern has a SSRF vulnerability in the CORS proxy middleware
medium6.9May 12, 2026CVE-2026-34522
SillyTavern has a path traversal in `/api/chats/import` allows arbitrary file write outside intended chat directory
high8.1Apr 1, 2026
