Is CVE-2026-44648 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44648 being exploited in the wild.

How severe is CVE-2026-44648?

High severity, with a CVSS score of 7.5, published 29 May 2026.

Which products and versions are affected?

sillytavern (npm) <= 1.17.0, SEMVER:introduced=0,fixed=1.18.0.

Is there a fix for CVE-2026-44648?

Yes. sillytavern (npm): upgrade to 1.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44648 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44648?

Check whether you run sillytavern (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44648: SillyTavern insufficient session expiration after password change

Q: Which products and versions are affected?

sillytavern (npm) <= 1.17.0, SEMVER:introduced=0,fixed=1.18.0.

Q: Is there a fix for CVE-2026-44648?

Yes. sillytavern (npm): upgrade to 1.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-44648 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-44648?

Check whether you run sillytavern (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44648 · Severity: high · CVSS 7.5 · Published 2026-05-29

SillyTavern is a user interface for interacting with text-generation AI models. A security flaw exists where changing an account password does not disconnect other active sessions. This means if an attacker manages to steal a user's login cookie, they can maintain permanent access to the account even after the legitimate owner resets their password, potentially exposing private conversations and API keys.

Technologies: sillytavern (npm). Vendors: npm.

Quick answers

Is CVE-2026-44648 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44648 being exploited in the wild.
How severe is CVE-2026-44648?: High severity, with a CVSS score of 7.5, published 29 May 2026.
Which products and versions are affected?: sillytavern (npm) <= 1.17.0, SEMVER:introduced=0,fixed=1.18.0.
Is there a fix for CVE-2026-44648?: Yes. sillytavern (npm): upgrade to 1.18.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44648 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44648?: Check whether you run sillytavern (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

sillytavern (npm): upgrade to 1.18.0 or later
```
npm install sillytavern@1.18.0
```

Technical details

SillyTavern utilizes stateless signed cookies via the cookie-session middleware to manage authentication. The application's password change and recovery endpoints (POST /api/users/change-password and POST /api/users/recover-step2) update the password hash in the database but do not implement a mechanism to revoke or expire existing session cookies. Because the session data is stored entirely on the client side, an attacker who has obtained a session cookie (e.g., via XSS or MITM) can continue to authenticate successfully until the cookie's natural expiration, which defaults to 400 days. This vulnerability is classified as CWE-613 (Insufficient Session Expiration). A fix was introduced in version 1.18.0.

Affected products

SillyTavern SillyTavern <= 1.17.0

Identifiers

CVE-2026-44648
GHSA-wmm3-h9qj-p5v6

Timeline

2026-05-11: disclosed
2026-05-12: advisory: GitHub Advisory published
2026-05-11: patched: Version 1.18.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.