CVE-2026-44652: SillyTavern SSRF in CORS proxy middleware

CVE-2026-44652 · Severity: medium · CVSS 4 · Published 2026-05-29

SillyTavern, a popular interface for large language models, contains a security flaw in its optional CORS proxy feature. This vulnerability allows an attacker to force the server to make unauthorized requests to internal network resources or sensitive metadata endpoints. If exploited, this could lead to the exposure of private internal data or allow an attacker to probe the local network where the application is hosted.

Technologies: sillytavern (npm). Vendors: npm.

Quick answers

Is CVE-2026-44652 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44652 being exploited in the wild.
How severe is CVE-2026-44652?
Medium severity, with a CVSS score of 4, 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-44652?
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-44652 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44652?
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 Server-Side Request Forgery (SSRF) vulnerability exists in SillyTavern's `corsProxyMiddleware` located at `src/middleware/corsProxy.js`. The component fails to validate the `url` parameter before passing it to the `fetch()` function, only blocking circular requests to its own host. An unauthenticated remote attacker can exploit this by sending crafted requests to the `/proxy/` endpoint to reach internal network services, loopback addresses, or cloud metadata services. This can result in the exfiltration of sensitive responses from internal infrastructure. The issue is addressed in version 1.18.0 by the introduction of a configurable private request whitelisting filter.

Affected products

  • SillyTavern SillyTavern <= 1.17.0

Identifiers

  • CVE-2026-44652
  • GHSA-ccfq-2454-f5xw

Timeline

  • 2026-05-11: disclosed
  • 2026-05-12: advisory: GitHub Advisory GHSA-ccfq-2454-f5xw 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.