sillytavern Known Vulnerabilities & Fixes
sillytavern has 3 known security vulnerabilities in npm (Node.js). Upgrade to version 1.18.0 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 1.18.0
Upgrading to 1.18.0 or later resolves all 3 known vulnerabilities in sillytavern. Run: npm install sillytavern@1.18.0
Is sillytavern in your project?
Check if you're affected and upgrade to 1.18.0 to stay secure.
Security Summary
- 3 affected version ranges have been identified across these 3 advisories.
- 100% of known issues have a published fixed version.
- Remediation: npm update sillytavern
Vulnerabilities
3 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Oct 6, 2025, most recently May 12, 2026 (218 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2026-44649 SillyTavern has Authentication Bypass via SSO Header Injection | CRITICAL | All versions | 1.18.0 |
| CVE-2025-59159 SillyTavern Web Interface Vulnerable DNS Rebinding | CRITICAL | All versions | 1.13.4 |
| CVE-2026-44650 SillyTavern has a Path Traversal issue | CRITICAL | All versions | 1.18.0 |
About This Data
Vulnerability data for sillytavern is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related npm (Node.js) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of sillytavern.