Quick answers
- Is CVE-2026-44650 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44650 being exploited in the wild.
- How severe is CVE-2026-44650?
- Critical severity, with a CVSS score of 9.1, 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-44650?
- 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-44650 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44650?
- 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
A path traversal vulnerability exists in the 'POST /api/extensions/delete' endpoint (and several related endpoints) due to improper input validation. The application uses the 'sanitize-filename' library, which converts a single dot (".") into an empty string. When this empty string is passed to 'path.join(basePath, "")', it resolves to the 'basePath' itself—the root extensions directory. Because the application performs a recursive deletion ('fs.promises.rm' with 'recursive: true') on the resulting path, an attacker can wipe the entire extensions folder. This requires no authentication in default configurations and can be exploited via a single HTTP request. The issue is fixed in version 1.18.0 by validating the input after sanitization.
Affected products
- SillyTavern SillyTavern <= 1.17.0
Identifiers
- CVE-2026-44650
- GHSA-886q-f44j-h6wh
Timeline
- 2026-05-11: advisory: GitHub Security Advisory published
- 2026-05-29: disclosed: CVE published to NVD
- 2026-05-29: patched: Vulnerability fixed in version 1.18.0