SSRF (Server-Side Request Forgery) in text-generation-webui (CVE-2026-35486)
Summary
SSRF in text-generation-webui (CVE-2026-35486). Confidential information can be exposed externally. Mitigation: upgrade to 4.3 or later.
Original description
The description as published by the source.
text-generation-webui is an open-source web interface for running Large Language Models. Prior to 4.3, he superbooga and superboogav2 RAG extensions fetch user-supplied URLs via requests.get() with zero validation — no scheme check, no IP filtering, no hostname allowlist. An attacker can access cloud metadata endpoints, steal IAM credentials, and probe internal services. The fetched content is exfiltrated through the RAG pipeline. This vulnerability is fixed in 4.3.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-35486 has been found in text-generation-webui.
Confidential information can be exposed externally.
What to do: upgrade text-generation-webui to 4.3 or later.
If unsure, ask your IT team or search "text-generation-webui CVE-2026-35486" on the vendor's site.
CVE-2026-35486 (text-generation-webui) — CWE-918
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 4.3 — 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 text-generation-webui.
Check the vendor advisory for the affected versions of text-generation-webui.
Severity: ?. Confidential information can be exposed externally.
Update to 4.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'text-generation-webui' . 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 'text-generation-webui' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
text-generation-webuiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade text-generation-webui to 4.3ステージング環境で 4.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov