CVE-2026-44650
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSillyTavern 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, POST /api/extensions/delete endpoint accepts extensionName: "." which bypasses sanitize-filename validation, causing the entire user extensions directory to be recursively deleted. No authentication is required in the default configuration. This vulnerability is fixed in 1.18.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSillyTavern versions prior to 1.18.0 have a path traversal vulnerability in the POST /api/extensions/delete endpoint where passing extensionName '.' bypasses sanitize-filename validation, allowing unauthenticated attackers to recursively delete the entire user extensions directory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm SillyTavern is runningCheck for SillyTavern processes or the application listening on its configured port (usually 8000 or 8080)Affected if SillyTavern is exposed and accessible on a network port
-
Identify the installed SillyTavern versionCheck the version.json file in the SillyTavern installation directory, or look at the web interface footer which often displays the versionAffected if The installed version is earlier than 1.18.0
-
Verify the default configuration is in useCheck if authentication is enabled in config.yaml or config.json. Look for 'auth' or 'authentication' settings set to false, or check if the config file is missingAffected if No authentication is configured (default configuration)
-
Check for the extensions directory existenceInspect the file system for the presence of the 'extensions' folder within the SillyTavern user data or installation directoryAffected if The extensions directory exists and contains user-installed extensions
-
Confirm the API endpoint is accessibleAttempt to reach the /api/extensions/delete endpoint or check if the SillyTavern web API is responding without authenticationAffected if The SillyTavern API is accessible without authentication
A defender is affected if SillyTavern version earlier than 1.18.0 is running with default configuration (no authentication) and the extensions directory is present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to SillyTavern 1.18.0 or later, and enable authentication if not already configured.
1.18.0
- Backup any custom extensions in the user extensions directory before upgrading
- Update SillyTavern to version 1.18.0 by pulling the latest release from the official repository
- Restart the SillyTavern service to ensure the patched version is running
- Verify the /api/extensions/delete endpoint no longer accepts '.' as a valid extension name
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44650 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44650 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data