dbcve.org
Open WebuiApplication · Openwebui

CVE-2026-59224

HIGH · 8.0 CVSS v3.1 Published 2026-07-09
Fix available
A fix is available. Upgrade to 0.10.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable Patch available 6 weeks old

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 an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.10.0, backend/open_webui/routers/terminals.py built the ws_terminal upstream URL from an unencoded session_id and appended user_id as a query parameter, allowing query injection to make the terminal backend resolve another user identity; the HTTP proxy path also forwarded X-User-Id as an integrity-unbound identity claim. This issue is fixed in version 0.10.0.

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

In backend/open_webui/routers/terminals.py, the session_id is not URL-encoded when constructing the WebSocket terminal upstream URL, and user_id is appended as a query parameter. This allows query injection to make the terminal backend resolve a different user identity. Additionally, the HTTP proxy path forwards the X-User-Id header as an integrity-unbound identity claim, enabling identity spoofing.

MitigationUpgrade to Open WebUI version 0.10.0 or later which properly URL-encodes the session_id and addresses the integrity-unbound X-User-Id identity claim in the proxy path.

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.10.0

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
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Open WebUI version
    Check the installed version of Open WebUI by reviewing the version file, Docker image tag, or the running application. Common locations include: the 'version' file in the installation directory, the Docker container tag, or the UI footer which sometimes displays the version.
    Affected if The installed version is lower than 0.10.0 (e.g., 0.9.x, 0.8.x, etc.)
  2. Locate the vulnerable terminal router file
    Search for the file backend/open_webui/routers/terminals.py in the Open WebUI installation directory. This file handles WebSocket terminal connections.
    Affected if The file exists and is present in versions below 0.10.0
  3. Inspect session_id handling in terminals.py
    Open backend/open_webui/routers/terminals.py and examine how the session_id is used when constructing the WebSocket upstream URL. Look for code that appends session_id or user_id to a URL without using URL encoding or proper escaping.
    Affected if The code shows session_id or user_id being directly concatenated into a URL string without URL encoding (e.g., no use of urllib.parse.quote or equivalent)
  4. Check for X-User-Id header forwarding in proxy configuration
    Examine the HTTP proxy configuration that handles terminal requests. Look for any proxy rules or middleware that forward the X-User-Id header from incoming requests to the backend without validation or binding to an authenticated session.
    Affected if The proxy configuration passes the X-User-Id header to the backend without cryptographic binding to the session identity
  5. Determine if terminal feature is accessible
    Verify whether the terminal functionality is enabled and accessible to users. This may involve checking if the /terminals endpoint is exposed, or if users have permissions to access terminal features within the web UI.
    Affected if Terminal functionality is enabled and accessible to non-admin users, and the version is below 0.10.0

You are affected if Open WebUI version is below 0.10.0 and the terminal feature is in use, with the vulnerable code handling session_id without proper URL encoding and forwarding the X-User-Id header unbound to session integrity.

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.10.0 or later
Fixed in 0.10.0
Vendor patch github.com →
Interim mitigation

Upgrade to Open WebUI version 0.10.0 or later which properly URL-encodes the session_id and addresses the integrity-unbound X-User-Id identity claim in the proxy path.

Recommended fix High confidence

Open WebUI version 0.10.0

  1. 1. Back up your current Open WebUI installation, including configuration files and any custom data.
  2. 2. Pull the latest version 0.10.0 of the Open WebUI container image, or update via your installation method (e.g., `docker pull open-webui/webui:latest` or appropriate version tag).
  3. 3. Stop the currently running Open WebUI instance.
  4. 4. Start the new container with the updated image.
  5. 5. Verify the application starts successfully and check logs for any errors.
  6. 6. Test terminal functionality to confirm the authentication fix is working properly.
Caveat Review the 0.10.0 release notes for any new features or configuration changes that may require adjustments

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

Fix this in Open Webui Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59224 — 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-59224 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