text-generation-webui hat eine SSRF in superbooga/superboogav2 Erweiterungen — keine URL-Validierung

The SSRF vulnerability in text-generation-webui arises from the superbooga and superboogav2 RAG extensions, which fetch user-supplied URLs without proper validation. Attackers can craft malicious URLs to access sensitive cloud metadata endpoints, such as those exposing AWS IAM credentials or Azure instance details. This could enable them to steal credentials, escalate privileges, and gain control over cloud resources. Furthermore, the vulnerability allows attackers to probe internal services behind firewalls, potentially mapping the internal network and identifying other vulnerable targets. The fetched content is then exfiltrated through the RAG pipeline, further amplifying the impact.

Organizations deploying text-generation-webui, particularly those running it in cloud environments or with access to sensitive internal resources, are at risk. Users relying on the superbooga or superboogav2 RAG extensions are especially vulnerable. Shared hosting environments where multiple users share the same text-generation-webui instance are also at increased risk.

• linux / server: Monitor access logs for requests to unusual or internal IP addresses, particularly metadata endpoints (169.254.169.254). Use journalctl to filter for requests originating from the RAG extensions.

journalctl -u text-generation-webui -g 'RAG extension' | grep '169.254.169.254'

• generic web: Use curl to test for endpoint exposure and potential SSRF. Attempt to access internal services via the web interface.

curl -v 'http://<text-generation-webui-ip>/rag/fetch?url=http://169.254.169.254/latest/meta-data/'

1. 2026-04-07Disclosure

   disclosure

1. Reserviert2026-04-02
2. Veröffentlicht2026-04-07
3. Geändert2026-04-09
4. EPSS aktualisiert2026-04-15

The primary mitigation for CVE-2026-35486 is to upgrade text-generation-webui to version 4.3.0 or later, which includes the necessary validation checks to prevent SSRF attacks. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) or proxy with strict URL filtering rules to block requests to suspicious domains or IP addresses. Additionally, restrict network access to the text-generation-webui instance to only authorized users and services. Regularly review and update the RAG extension configurations to ensure they adhere to security best practices.