Summary
SillyTavern has a SSRF vulnerability in the CORS proxy middleware
Impact
An attacker may access internal network services or metadata endpoints and exfiltrate sensitive responses.
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
- Enforce strict destination allowlist for proxy targets.
- Block loopback, link-local, RFC1918, and metadata address ranges.
- Apply the same destination validation to redirects.
Frequently Asked Questions
- What is CVE-2026-44652? CVE-2026-44652 is a medium-severity server-side request forgery (SSRF) vulnerability in sillytavern (npm), affecting versions <= 1.17.0. It is fixed in 1.18.0. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- Which versions of sillytavern are affected by CVE-2026-44652? sillytavern (npm) versions <= 1.17.0 is affected.
- Is there a fix for CVE-2026-44652? Yes. CVE-2026-44652 is fixed in 1.18.0. Upgrade to this version or later.
- Is CVE-2026-44652 exploitable, and should I be worried? Whether CVE-2026-44652 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-44652 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-44652? Upgrade
sillytavernto 1.18.0 or later.