Open WebUI /audio/api/v1/transcriptions में मनमाना फ़ाइल अपलोड के माध्यम से रिमोट कोड एग्जीक्यूशन की अनुमति देता है

The vulnerability lies in the /audio/api/v1/transcriptions endpoint, where the application fails to adequately validate the file.content_type and allows user-controlled filenames. An attacker, after authenticating, can leverage this to perform a path traversal, effectively overwriting files within the Docker container's filesystem. This is particularly concerning as OpenWebUI is often deployed within containerized environments, and successful file overwrites could lead to complete system compromise. The attacker could potentially inject malicious code, establish persistent backdoors, or exfiltrate sensitive data. The ability to execute code as root significantly expands the attack surface and potential impact.

Organizations deploying OpenWebUI within Docker containers, particularly those using it for sensitive audio processing tasks, are at significant risk. Shared hosting environments where OpenWebUI is installed could also be vulnerable if multiple users share the same container.

• linux / server: Monitor Docker container logs for unusual file creation or modification activity, particularly within the OpenWebUI application directory. Use journalctl -u openwebui to check for suspicious API calls.

journalctl -u openwebui | grep '/audio/api/v1/transcriptions'

• generic web: Monitor web server access logs for requests to /audio/api/v1/transcriptions with unusual or unexpected Content-Type headers.

grep '/audio/api/v1/transcriptions' /var/log/apache2/access.log

• python: If you have access to the OpenWebUI source code, review the /audio/api/v1/transcriptions endpoint for inadequate file validation logic.

1. 2025-03-20Disclosure

   disclosure

1. आरक्षित2024-08-21
2. प्रकाशित2025-03-20
3. संशोधित2025-10-15
4. EPSS अद्यतन2026-04-02

The primary mitigation is to upgrade OpenWebUI to version 0.5.17 or later, which addresses the file validation issue. If immediate upgrading is not feasible, consider implementing a Web Application Firewall (WAF) rule to block requests to the /audio/api/v1/transcriptions endpoint or restrict allowed file types and sizes. Additionally, review and harden the Docker container configuration to minimize the potential impact of a successful file overwrite. Implement strict file permissions within the container to limit the attacker's ability to execute overwritten files. Regularly scan container images for vulnerabilities.