SillyTavern: Existing sessions are not invalidated after password change, allowing session reuse and account takeover
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.5epss 0.4%
from disclosure to weapon0 days
Published on NVDMay 29
1st PoCMay 8
exploitation probability
0.4%top 67% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. Prior to 1.18.0, 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. This vulnerability is fixed in 1.18.0.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
Affected products
SillyTavern · SillyTavernpublic PoCs found — 1
githubgithub.com/zzzm0919/CVE-2026-44648★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.