Any open-webui instance ≤ 0.3.21 exposed to the network can be taken offline with a single unauthenticated HTTP request targeting three core endpoints including RAG document ingestion and audio transcription. No authentication is required to trigger resource exhaustion — trivial to script and automate. Immediately restrict network access to trusted IPs and apply rate-limiting on multipart upload endpoints; no official patch is currently listed.
Risk Assessment
HIGH. Zero authentication barrier combined with network accessibility and high impact on core AI functionality makes this a priority for any organization running open-webui. The attack requires no AI/ML knowledge — just a crafted HTTP POST with a padded multipart boundary. Risk escalates significantly for internet-facing deployments or instances accessible from untrusted internal segments. Absence of a listed patch version extends the exposure window, leaving network controls as the only current mitigation.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| open-webui | npm | <= 0.3.21 | No patch |
| open-webui | pip | <= 0.3.21 | No patch |
Severity & Risk
Attack Surface
Recommended Action
6 steps-
IMMEDIATE
Restrict access to /ollama/models/upload, /audio/api/v1/transcriptions, and /rag/api/v1/doc via firewall or reverse proxy ACLs to trusted IPs only.
-
Deploy WAF or rate-limiting rules targeting multipart/form-data POST requests to these endpoints.
-
Place open-webui behind an authenticating reverse proxy (e.g., Nginx + OAuth2-proxy or basic auth) as an interim control if internet-facing.
-
Set OS-level resource limits (CPU/memory cgroups, ulimits) on the open-webui process to contain blast radius.
-
Monitor GitHub releases for open-webui > 0.3.21 and prioritize patching immediately on release.
-
DETECTION
Alert on sustained CPU/memory spikes from the open-webui process correlated with high-rate multipart POST requests to affected endpoints.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is GHSA-5ccf-884p-4jjq?
Any open-webui instance ≤ 0.3.21 exposed to the network can be taken offline with a single unauthenticated HTTP request targeting three core endpoints including RAG document ingestion and audio transcription. No authentication is required to trigger resource exhaustion — trivial to script and automate. Immediately restrict network access to trusted IPs and apply rate-limiting on multipart upload endpoints; no official patch is currently listed.
Is GHSA-5ccf-884p-4jjq actively exploited?
No confirmed active exploitation of GHSA-5ccf-884p-4jjq has been reported, but organizations should still patch proactively.
How to fix GHSA-5ccf-884p-4jjq?
1. IMMEDIATE: Restrict access to /ollama/models/upload, /audio/api/v1/transcriptions, and /rag/api/v1/doc via firewall or reverse proxy ACLs to trusted IPs only. 2. Deploy WAF or rate-limiting rules targeting multipart/form-data POST requests to these endpoints. 3. Place open-webui behind an authenticating reverse proxy (e.g., Nginx + OAuth2-proxy or basic auth) as an interim control if internet-facing. 4. Set OS-level resource limits (CPU/memory cgroups, ulimits) on the open-webui process to contain blast radius. 5. Monitor GitHub releases for open-webui > 0.3.21 and prioritize patching immediately on release. 6. DETECTION: Alert on sustained CPU/memory spikes from the open-webui process correlated with high-rate multipart POST requests to affected endpoints.
What systems are affected by GHSA-5ccf-884p-4jjq?
This vulnerability affects the following AI/ML architecture patterns: LLM inference servers, RAG pipelines, AI model serving, web-based AI interfaces, audio transcription pipelines.
What is the CVSS score for GHSA-5ccf-884p-4jjq?
GHSA-5ccf-884p-4jjq has a CVSS v3.1 base score of 7.5 (HIGH).
Technical Details
NVD Description
A Denial of Service (DoS) vulnerability exists in open-webui/open-webui version 0.3.21. This vulnerability affects multiple endpoints, including `/ollama/models/upload`, `/audio/api/v1/transcriptions`, and `/rag/api/v1/doc`. The application processes multipart boundaries without authentication, leading to resource exhaustion. By appending additional characters to the multipart boundary, an attacker can cause the server to parse each byte of the boundary, ultimately leading to service unavailability. This vulnerability can be exploited remotely, resulting in high CPU and memory usage, and rendering the service inaccessible to legitimate users.
Exploitation Scenario
An external attacker discovers an open-webui instance via Shodan or internal network scan. They craft a multipart HTTP POST to /rag/api/v1/doc with a boundary string padded with thousands of additional characters — a single-line curl command. The server's multipart parser processes each byte of the extended boundary, consuming disproportionate CPU cycles per request. The attacker runs a simple script firing concurrent requests, exhausting server resources within seconds and rendering the entire AI assistant — chat, document ingestion, model management — unavailable. No credentials, no prior knowledge of the target's AI stack, no cleanup required.
Weaknesses (CWE)
CVSS Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H References
Timeline
Related Vulnerabilities
CVE-2026-44551 9.1 open-webui: LDAP auth bypass — full account takeover
Same package: open-webui CVE-2026-44552 8.7 open-webui: Redis cache poisoning enables cross-instance tool hijack
Same package: open-webui CVE-2025-64495 8.7 Open WebUI: XSS-to-RCE via malicious prompt injection
Same package: open-webui CVE-2025-65958 8.5 open-webui: SSRF allows internal network access
Same package: open-webui CVE-2024-7990 8.4 open-webui: Stored XSS enables admin session hijack
Same package: open-webui
AI Threat Alert