# CVE-2026-44565: Open WebUI: Open WebUI Arbitrary File Write, Delete via Path Traversal

> Attackers can write or delete arbitrary files on the server via path traversal in audio uploads, potentially leading to code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2026
- **Updated:** 18 May 2026
- **Also known as:** GHSA-j3fw-wc48-29g3, PYSEC-2026-2737

## What is CVE-2026-44565?

CVE-2026-44565 is a high-severity path traversal vulnerability in Openwebui Open Webui, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.6.10, when uploading an audio file, the name of the file is derived from the original HTTP upload request and is not validated or sanitized. This allows for users to upload files with names containing dot-segments in the file path and traverse out of the intended uploads directory. Effectively, users can upload files anywhere on the filesystem the user running the web server has permission. This vulnerability is fixed in 0.6.10.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-44565?

3 open source packages ship an affected version, including open-webui. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `open-webui` | PyPI | All versions | 0.6.10 |
| `open-webui` | PyPI | All versions | 0.6.10 |
| `open-webui` | PyPI | All versions | 0.6.10 |

Products: Openwebui Open Webui.

## How do I fix CVE-2026-44565?

Upgrade open-webui to 0.6.10 or later.

## Is CVE-2026-44565 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44565 exists.

## Other vulnerabilities in Openwebui Open Webui

- [CVE-2026-44551](https://insights.sbomify.com/CVE-2026-44551/): Open WebUI: LDAP Empty Password Authentication Bypass (critical 9.1)
- [CVE-2026-56400](https://insights.sbomify.com/CVE-2026-56400/): open-webui - Remote Code Execution via CORS Misconfiguration and Session Validation (critical 9.0)
- [CVE-2024-8017](https://insights.sbomify.com/CVE-2024-8017/): Cross-site Scripting (XSS) in open-webui/open-webui (critical 9.0)
- [CVE-2026-45672](https://insights.sbomify.com/CVE-2026-45672/): Open WebUI: Jupyter code execution works despite `ENABLE_CODE_EXECUTION=false` — feature gate bypassed (high 8.8)
- [CVE-2026-87995](https://insights.sbomify.com/CVE-2026-87995/): Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44565 and fix it if it is affected.

What it is: CVE-2026-44565 is a high-severity path traversal vulnerability in Openwebui Open Webui, published on 15 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44565 exists.

Affected packages and fixed versions:
- open-webui (PyPI): affected all versions; fixed in 0.6.10
- open-webui (PyPI): affected all versions; fixed in 0.6.10
- open-webui (PyPI): affected all versions; fixed in 0.6.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44565/ (Markdown: https://insights.sbomify.com/CVE-2026-44565/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44565
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44565
- OSV: https://osv.dev/vulnerability/CVE-2026-44565

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44565/
Summaries are generated and may contain mistakes; the official description above is the record.