SSRF (Server-Side Request Forgery) in sillytavern (CVE-2026-44652)
Summary
SSRF in sillytavern (CVE-2026-44652). Risk of unauthorized operations or information disclosure. Exploitable via GET /proxy/. Mitigation: upgrade to 1.18.0 or later.
Original description
The description as published by the source.
SillyTavern 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, 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. This vulnerability is fixed in 1.18.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44652 has been found in sillytavern.
Attackers can target a specific entry point like GET /proxy/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade sillytavern to 1.18.0 or later.
If unsure, ask your IT team or search "sillytavern CVE-2026-44652" on the vendor's site.
CVE-2026-44652 (sillytavern) — CWE-918
Attack surface: GET /proxy/ / corsProxyMiddleware / req.params.url
Patched: 1.18.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in sillytavern. Attackers reach the vulnerable code path via GET /proxy/.
Check the vendor advisory for the affected versions of sillytavern. Attack surface: GET /proxy/ / corsProxyMiddleware / req.params.url.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.18.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /proxy/ requests with malformed payloads or SQL meta-characters. Run grep -r 'sillytavern' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sillytavern' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sillytavernを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /proxy/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /proxy/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade sillytavern to 1.18.0ステージング環境で 1.18.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /proxy/ on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com