Products / open-webui
open-webui
165 records.
- Open WebUI: Non-admin users can delete admin-owned external knowledge connections via knowledge base deletion Deleting a knowledge base also deletes its shared admin-owned vector connection without checking the caller's role or other dependent bases.
- Open WebUI: Any authenticated user can reach the Azure platform channel via server-side web fetch The internal-address screen treats the Azure platform channel address as public, so authenticated users can reach it through URL fetches.
- Open WebUI: Unauthenticated requests can stall the server via uncached OIDC fetches in back-channel logout An unauthenticated back-channel logout request triggers uncached, blocking OIDC discovery and key fetches on the event loop, so repeated requests stall the server.
- Open WebUI: Any authenticated user can inject chats into another user's folder via chat completions The chat-completions endpoint saves new chats into a folder named in the request without checking the caller's write permission on that folder.
- Open WebUI: Users denied by the OAuth domain allowlist or role policy can still sign in via token exchange The token exchange endpoint skips the email domain allowlist, so users removed from allowed domains still receive working sessions.
- Open WebUI: SSRF into internal services via DNS rebinding in the Playwright web loader The URL check resolves the hostname once but the Playwright browser resolves it again, so a DNS answer that changes between lookups reaches internal addresses.
- Open WebUI: Any authenticated user can start a non-terminating request via a folder parent cycle Re-parenting a folder beneath its own descendant creates a cycle, and the tree walk never tracks visited nodes, so the request never terminates.
- Open WebUI: Channel members can overwrite another member's message via the chat completions endpoint A channel member can rewrite another member's message through the chat completions path, which skips the authorship check that the dedicated edit route applies.
- Open WebUI: Same-origin XSS to account takeover via terminal port-preview iframe hardcoding allow-same-origin
- Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication
- Open WebUI: Inaccessible knowledge bases are exposed through the built-in knowledge tool on most vector backends
- Open WebUI: Any authenticated user can suppress calendar alerts instance-wide via a non-numeric alert value
- Open WebUI: Admin demoted through SSO role sync keeps read and write access to all users' notes
- Open WebUI: Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite
- Open WebUI: Users denied by the OAuth role policy can still sign in via token exchange
- Open WebUI: Any authenticated user can hang the server via message deletion in a cyclic chat tree A chat whose messages reference each other as children makes the message-deletion walk loop forever, blocking the server's event loop.
- Open WebUI: Server-side fetches reach blocked and internal hosts via unvalidated HTTP redirect targets Redirect targets from server-side page fetches skip the blocked-host and private-address checks, so authenticated users can reach internal services.
- Open WebUI: Any authenticated user can hang the server via a cyclic chat message history
- Open WebUI: Any authenticated user can stall a worker via a knowledge-search pattern that backtracks catastrophically A chat user can get the model to run a catastrophic-backtracking regex against knowledge files, and no timeout stops it from pinning a worker.
- Open WebUI: A folder write-collaborator can permanently delete the owner's chats by deleting a shared subfolder Write access on a shared subfolder lets a collaborator delete the owner's chats, because the delete handler checks write access rather than ownership.
- Open WebUI: Tool source code disclosed to read-only users via the tool list and get endpoints Read endpoints for shared tools return the full Python source to non-writer users, exposing any credentials or internal URLs embedded in the code.
- Open WebUI: Any authenticated user can cancel another user's chat generation via the chat delete endpoint The chat delete endpoint cancels another user's in-flight generation tasks before checking whether the caller may delete that chat.
- Open WebUI: Same-origin XSS to account takeover via terminal file-preview iframe hardcoding allow-same-origin Terminal-served HTML previews run in an iframe that grants same-origin access, so scripts in the file run in the app origin and can read the session token.
- Open WebUI: Unapproved accounts can open terminal sessions via a WebSocket auth path missing the role check
- Open WebUI: Cross-user file content disclosure via request-scoped direct model knowledge metadata Knowledge attached to an inline model skips the access check, so an authenticated user who knows another user's file ID can retrieve its indexed content.
- Open WebUI: Instance-wide stall via automation recurrence rules that force multi-second parsing Minutely recurrence rules force the parser to enumerate decades of occurrences synchronously on the event loop, stalling the server for every user.
- Open WebUI: Any authenticated user can reach internal services and cloud metadata via NAT64-encoded URLs A NAT64-wrapped IPv4 literal passes a globally-routable check that only inspects the IPv6 form, letting the server fetch internal and metadata endpoints.
- Open WebUI: Users denied the image-generation permission can still generate images via chat completions Chat completion requests can include an image feature flag that the server honours without rechecking the user's revoked permission, so generation still runs.
- Open WebUI: DNS Rebinding SSRF Bypass
- Open WebUI: Deletion of directories and file embeddings in other knowledge bases via sync cleanup
- Open WebUI: Any member with write access to a standard channel can edit or delete other members' messages
- Open WebUI: Stored XSS via unescaped KaTeX render-error fallback in rendered messages
- Open WebUI: Client-side SSRF via unrestricted external resource loading in Vega/Vega-Lite chart rendering
- Open WebUI: Account takeover via OAuth token exchange accepting tokens issued to any client
- Open WebUI: SSRF into internal services via unvalidated sub-resource requests in the Playwright web loader
- Open WebUI: Model meta.knowledge read-only file access can be upgraded to file write/delete A model's knowledge-file metadata lets a read-only grant satisfy later write and delete checks, because an earlier fix validated only read access.
- Open WebUI: Cross-user model-list exposure via static cache key in get_all_models (aiocache key= vs key_builder= misuse) A misused cache key stores per-user permission-filtered model lists under one shared key, so a different user can receive them within the TTL.
- Open WebUI: Stored web worker XSS via Pyodide A chat message carrying Python code runs in a same-origin worker when a victim clicks Run, letting it make authenticated requests as that user.
- Open WebUI: Private channel messages can be disclosed through cross-channel thread parent_id binding A low-privilege user requests a thread in an accessible channel and supplies a message id from a private channel as the root, so the parent message is returned without a channel membership check.
- Open WebUI: Cross-user code-interpreter and tool execution via unvalidated Socket.IO event-caller session_id A user supplies another user's socket session id, so code and tool calls run in the victim's session and can reach admin-only server-side function execution.
- Open WebUI: Upload `metadata.knowledge_id` bypasses the knowledge-base write-access check (read-only users can add files to KB) An upload carrying a knowledge base ID is linked to that knowledge base before the write-permission check runs, letting read-only users add files.
- Open WebUI: Account enumeration via observable login timing discrepancy Login responses are slower for registered emails because password hashing runs only for existing accounts, revealing which addresses are registered.
- Open WebUI: Realtime endpoints accept Redis-revoked JWTs after signout/backchannel logout Realtime socket and terminal endpoints check only JWT signature and expiry, not the revocation store, so signed-out tokens can still connect.
- Open WebUI: ReDoS in skill-mention regexes causes whole-instance DoS on default config
- open-webui terminal proxy path traversal guard bypass via 9x encoded traversal Traversal sequences encoded nine times survive the proxy's limited decoding loop, so requests reach terminal server paths outside the permitted proxy prefix.
- Open WebUI: /api/v1/channels/{id}/members exposes full user model including sensitive credentials
- Open WebUI: Unauthenticated WebSocket Access to Collaborative Document Handlers (ydoc:awareness:update, ydoc:document:leave)
- Open WebUI: Terminal proxy forwards a spoofable, integrity-unbound user identity to the upstream (X-User-Id header and ws_terminal session_id query injection)
- Open WebUI: Arena task endpoints can bypass underlying model access controls
- Open WebUI: Scheduled automations continue after pending-user deactivation and stored model ACL revocation