CVE-2026-44652: SillyTavern has a SSRF vulnerability in the CORS proxy middleware
Resolution SillyTavern 1.18.0 added a generic server-side request filter (Private Request Whitelisting). Since we expect users to use the application in a trusted environment, the filter is disabled by default, however it is strongly advised to be enabled and properly configured when an instance is being hosted over a network, as suggested by a console warning message and an officially published security checklist…
Published May 12, 2026 · Updated Jun 9, 2026
Affected packages
sillytavern
- Ecosystem
- npm
- Affected
- <= 1.17.0
- Fixed in
- 1.18.0
- Check
npm ls sillytavern
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Resolution
SillyTavern 1.18.0 added a generic server-side request filter (Private Request Whitelisting). Since we expect users to use the application in a trusted environment, the filter is disabled by default, however it is strongly advised to be enabled and properly configured when an instance is being hosted over a network, as suggested by a console warning message and an officially published security checklist for administrators.
Documentation:
- https://docs.sillytavern.app/administration/config-yaml/#private-address-whitelisting
- https://docs.sillytavern.app/administration/#security-checklist
Note on future SSRF findings
Since the request filter applies to the entire application, no SSRF vulnerabilities against individual endpoints will be accepted, unless it has been proven that a properly configured and enabled filter can be bypassed in an undocumented way. Only advisories disclosed before the 1.18.0 release will be posted if their concern is SSRF.
Overview
- Vulnerability Type: SSRF
- Affected Location:
src/middleware/corsProxy.js:31 - Trigger Scenario: SSRF in optional CORS proxy
Root Cause
corsProxyMiddleware forwards req.params.url directly into fetch(url, ...). It only blocks circular requests to its own host and does not enforce destination allowlist or private/loopback restrictions, enabling SSRF.
Source-to-Sink Chain
- Source (user-controlled input)
- Entry point:
GET /proxy/:url(*)
- Data flow
- Code analysis shows concrete propagation into this sink:
- vulnerability title:
SSRF in optional CORS proxy - sink location reached by attacker-controlled input:
src/middleware/corsProxy.js:31 - The same sink behavior is confirmed by controlled execution observations.
- Sink (dangerous operation)
- Sink location:
src/middleware/corsProxy.js:31 - Vulnerable behavior: SSRF in optional CORS proxy
Exploitation Preconditions
- The attacker can control or influence a URL/endpoint parameter.
- The server can access internal or sensitive network targets.
- Outbound request validation or redirect controls are insufficient.
Risk
This issue can be used to pivot network access and reach unintended internal resources.
Impact
An attacker may access internal network services or metadata endpoints and exfiltrate sensitive responses.
Remediation
- Enforce strict destination allowlist for proxy targets.
- Block loopback, link-local, RFC1918, and metadata address ranges.
- Apply the same destination validation to redirects.
Credited to FORIMOC.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-46372
SillyTavern: SSRF in SearXNG Search Proxy via Unvalidated baseUrl
high8.5May 19, 2026CVE-2026-44648
SillyTavern: Existing sessions are not invalidated after password change, allowing session reuse and account takeover
high7.5May 12, 2026CVE-2026-44649
SillyTavern has Authentication Bypass via SSO Header Injection
critical9.8May 12, 2026CVE-2026-44650
SillyTavern has a Path Traversal issue
critical9.1May 12, 2026CVE-2026-44651
SillyTavern has a reflected XSS vulnerability in the CORS proxy middleware
medium6.9May 12, 2026CVE-2026-34522
SillyTavern has a path traversal in `/api/chats/import` allows arbitrary file write outside intended chat directory
high8.1Apr 1, 2026
