Summary
Open WebUI contains a privilege escalation vulnerability in its terminal proxy that can let an authenticated user access administrator terminal APIs with a shared key attached. Under affected configurations, attackers may control other users' terminals, change terminal policies, or inject environment variables through crafted proxy requests.
Open WebUI contains a privilege escalation vulnerability in its terminal proxy that can let an authenticated user access administrator terminal APIs with a shared key attached. Under affected configurations, attackers may control other users' terminals, change terminal policies, or inject environment variables through crafted proxy requests.
Affected context
The issue occurs in Open WebUI deployments using the vulnerable terminal proxy implementation. Authenticated users may be able to submit requests through the terminal proxy endpoint and reach administrative terminal operations because authorization is not adequately enforced between the requesting user, the target terminal, and the administrator API. The affected release range is Open WebUI 0.8.6 through versions before 0.11.4.
The issue occurs in Open WebUI deployments using the vulnerable terminal proxy implementation. Authenticated users may be able to submit requests through the terminal proxy endpoint and reach administrative terminal operations because authorization is not adequately enforced between the requesting user, the target terminal, and the administrator API. The affected release range is Open WebUI 0.8.6 through versions before 0.11.4.
Exploit preconditions
- Attack surface: The terminal proxy endpoint at
/api/v1/terminals/{server_id}/{path} - Required access: A valid authenticated Open WebUI user account
- Trigger point: A request routed through the terminal proxy to terminal administration functionality
- Why exploitation is possible: The proxy attaches a shared administrator key without sufficiently verifying whether the authenticated user is authorized to act on the selected terminal or administrative operation
- Attack surface: The terminal proxy endpoint at
/api/v1/terminals/{server_id}/{path} - Required access: A valid authenticated Open WebUI user account
- Trigger point: A request routed through the terminal proxy to terminal administration functionality
- Why exploitation is possible: The proxy attaches a shared administrator key without sufficiently verifying whether the authenticated user is authorized to act on the selected terminal or administrative operation
Why this happens
The vulnerability results from missing authorization checks at a proxy boundary. A request accepted from an authenticated user is forwarded with elevated credentials, while authorization is not consistently evaluated against the target terminal, operation, and owning user. This behavior maps to CWE-862: Missing Authorization, in which an application fails to enforce an access control decision before permitting a protected action.
The vulnerability results from missing authorization checks at a proxy boundary. A request accepted from an authenticated user is forwarded with elevated credentials, while authorization is not consistently evaluated against the target terminal, operation, and owning user. This behavior maps to CWE-862: Missing Authorization, in which an application fails to enforce an access control decision before permitting a protected action.
Potential impact
- An attacker may list terminals belonging to other users.
- An attacker could stop or otherwise disrupt other users' terminals.
- An attacker may modify terminal policies outside their authorized scope.
- Injected environment variables could alter the behavior of other users' terminal sessions.
- The vulnerability could support unauthorized access to terminal-associated data or workflows.
- An attacker may list terminals belonging to other users.
- An attacker could stop or otherwise disrupt other users' terminals.
- An attacker may modify terminal policies outside their authorized scope.
- Injected environment variables could alter the behavior of other users' terminal sessions.
- The vulnerability could support unauthorized access to terminal-associated data or workflows.
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every terminal proxy operation and preventing shared administrative credentials from bypassing user-level access controls.
Common defensive patterns include:
- Validate the authenticated user's ownership or delegated permissions for every target terminal and action.
- Apply deny-by-default authorization checks before proxying requests.
- Avoid exposing administrator API credentials to general user request paths.
- Use narrowly scoped, short-lived service credentials when proxying is necessary.
- Enforce tenant and user isolation for terminal resources, policies, and environment data.
- Record and review administrative terminal actions, including the requesting identity and target resource.
- Run terminal services with the minimum permissions required for their intended functions.
Mitigation generally focuses on enforcing authorization at every terminal proxy operation and preventing shared administrative credentials from bypassing user-level access controls.
Common defensive patterns include:
- Validate the authenticated user's ownership or delegated permissions for every target terminal and action.
- Apply deny-by-default authorization checks before proxying requests.
- Avoid exposing administrator API credentials to general user request paths.
- Use narrowly scoped, short-lived service credentials when proxying is necessary.
- Enforce tenant and user isolation for terminal resources, policies, and environment data.
- Record and review administrative terminal actions, including the requesting identity and target resource.
- Run terminal services with the minimum permissions required for their intended functions.
How teams detect issues like this
Organizations can look for this vulnerability class through:
- Static analysis and code review checks for proxy handlers that forward privileged credentials.
- Review of authorization decisions at every route, resource, and operation boundary.
- Tests confirming that users cannot access, stop, or modify terminals owned by other users.
- API gateway or policy rules restricting terminal administration routes to explicitly authorized identities.
- Audit-log analysis for cross-user terminal access, unexpected policy changes, and unusual environment-variable modifications.
- Automated security review tools that flag shared-key use, missing object-level authorization, and inconsistent access-control enforcement.
Organizations can look for this vulnerability class through:
- Static analysis and code review checks for proxy handlers that forward privileged credentials.
- Review of authorization decisions at every route, resource, and operation boundary.
- Tests confirming that users cannot access, stop, or modify terminals owned by other users.
- API gateway or policy rules restricting terminal administration routes to explicitly authorized identities.
- Audit-log analysis for cross-user terminal access, unexpected policy changes, and unusual environment-variable modifications.
- Automated security review tools that flag shared-key use, missing object-level authorization, and inconsistent access-control enforcement.
