issue: user setting overrules model settings for websearch #6302

New Issue

GiteaMirror · 2025-11-11T16:50:31-06:00

GiteaMirror commented

2025-11-11 16:50:31 -06:00

Originally created by @Maximilian-Pichler on GitHub (Sep 2, 2025).

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.26

Ollama Version (if applicable)

none

Operating System

linux

Browser (if applicable)

any

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

We have encountered an issue related to model configuration and tool access permissions.

Expected Behavior:
Model-level restrictions on tool access (such as Websearch) should not be bypassed by global user settings.

Actual Behavior

Actual Behavior:
Global "always use websearch" setting overrides the custom model's configuration, enabling Websearch where it should be explicitly disabled.

Steps to Reproduce

Steps to Reproduce:

In our workspace, we created a custom model and explicitly disabled the Websearch tool for most models, to prevent scenarios where users might upload internal documents whose content could be sent to our external search API provider (not trusted for internal data).
Our intended setup is:
For models with Websearch enabled, file upload is disabled.
For models with file upload enabled, Websearch is disabled.
Issue:
If a user sets the application-wide setting to "always use websearch," this setting overrides model-specific tool restrictions. As a result, Websearch is used even with custom models that should not have access to this tool. This poses a potential security risk, as internal documents could be exposed to third parties via the websearch API.

Logs & Screenshots

none

Additional Information

It's unclear if this behavior is intentional, but it was unexpected from our point of view.

Originally created by @Maximilian-Pichler on GitHub (Sep 2, 2025). ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.26 ### Ollama Version (if applicable) none ### Operating System linux ### Browser (if applicable) any ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior We have encountered an issue related to model configuration and tool access permissions. Expected Behavior: Model-level restrictions on tool access (such as Websearch) should not be bypassed by global user settings. ### Actual Behavior Actual Behavior: Global "always use websearch" setting overrides the custom model's configuration, enabling Websearch where it should be explicitly disabled. ### Steps to Reproduce Steps to Reproduce: In our workspace, we created a custom model and explicitly disabled the Websearch tool for most models, to prevent scenarios where users might upload internal documents whose content could be sent to our external search API provider (not trusted for internal data). Our intended setup is: For models with Websearch enabled, file upload is disabled. For models with file upload enabled, Websearch is disabled. Issue: If a user sets the application-wide setting to "always use websearch," this setting overrides model-specific tool restrictions. As a result, Websearch is used even with custom models that should not have access to this tool. This poses a potential security risk, as internal documents could be exposed to third parties via the websearch API. ### Logs & Screenshots none ### Additional Information It's unclear if this behavior is intentional, but it was unexpected from our point of view.

GiteaMirror added the bug label 2025-11-11 16:50:31 -06:00

GiteaMirror closed this issue

2025-11-11 16:50:31 -06:00

GiteaMirror commented

2025-11-11 16:50:32 -06:00

@tjbck commented on GitHub (Sep 6, 2025):

Addressed with 9368d0ac75

@tjbck commented on GitHub (Sep 6, 2025): Addressed with 9368d0ac751ec3072d5a96712b80a9b20a642ce6

GiteaMirror referenced this issue

2026-04-19 20:43:14 -05:00

[GH-ISSUE #6302] pip install open-webui fails #14311

GiteaMirror referenced this issue