dbcve.org
Open WebuiApplication · Openwebui

CVE-2026-54017

HIGH · 7.7 CVSS v3.1 Published 2026-06-18
Fix available
A fix is available. Upgrade to 0.9.6 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.9.6, the terminal-server reverse proxy in `backend/open_webui/routers/terminals.py` does not fully confine the user-controlled `path` segment before forwarding it to an admin-configured terminal server. An authenticated user who has been granted access to a terminal server can craft `path` values containing encoded `../` traversal sequences that escape the intended path (or policy) scope on that server, reaching unintended endpoints and files on the terminal-server host. Where the terminal server fans requests out to internal services, this also gives SSRF-style reach into those services. This is a separate code path from the `/api/v1/retrieval/process/web` SSRF (GHSA-c6xv-rcvw-v685), with its own input. Two distinct vectors are consolidated here: first, raw path forwarding / single-encoded traversal (original report); and second, a bypass of the subsequently-added `_sanitize_proxy_path` mitigation using double-encoded dots (`%252e%252e`). The attacker-controlled input is the request `path`, supplied by the non-admin user, not anything an administrator configures, so this is not an admin-trust / Rule-9 situation. Version 0.9.6 fixes the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Open WebUI's terminal-server reverse proxy in backend/open_webui/routers/terminals.py fails to properly sanitize user-controlled path segments before forwarding requests to admin-configured terminal servers. Authenticated users with terminal access can inject encoded ../ traversal sequences (both single-encoded like %2e%2e and double-encoded like %252e%252e) to escape the intended path scope, enabling arbitrary file access and SSRF-style attacks against internal services reachable from the terminal server.

MitigationUpgrade to Open WebUI version 0.9.6 or later which implements proper path sanitization that handles both single and double-encoded traversal sequences.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Open WebuiApplication
Affected:< 0.9.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Open WebUI version
    Check the installed version of Open WebUI by inspecting the package version (e.g., pip show open-webui, docker image tag, or package.json version)
    Affected if Installed version is less than 0.9.6
  2. Confirm terminal-server feature is enabled
    Inspect whether the terminal-server functionality is active in the deployment - check for terminal-related router configuration in backend/open_webui/routers/ or if the /terminals endpoint is exposed
    Affected if Terminal-server reverse proxy is accessible and authenticated users can access it
  3. Check for admin-configured terminal servers
    Review the Open WebUI configuration for any admin-configured upstream terminal server URLs that the reverse proxy forwards to (check config files, environment variables, or admin settings)
    Affected if One or more terminal server endpoints are configured as upstream targets
  4. Inspect the vulnerable code path
    Examine backend/open_webui/routers/terminals.py for path handling logic - look for code that processes user-supplied path segments without proper sanitization of encoded traversal sequences (%2e%2e or %252e%252e)
    Affected if The code processes path segments from requests without validating for encoded ../ sequences

The environment is affected if Open WebUI version is below 0.9.6 AND the terminal-server feature is enabled with at least one upstream terminal server configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.9.6 or later
Fixed in 0.9.6
Interim mitigation

Upgrade to Open WebUI version 0.9.6 or later which implements proper path sanitization that handles both single and double-encoded traversal sequences.

Recommended fix High confidence

0.9.6

  1. Backup the current Open WebUI installation and any persistent data
  2. Upgrade Open WebUI to version 0.9.6
  3. Verify the upgrade by checking the installed version matches 0.9.6
  4. Test that the terminal-server endpoint properly blocks path traversal attempts with `../` sequences

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Open Webui Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54017 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data