Open WebUI v0.12.5 Released with Security Patches and Multi-Page Notes

- 1. At a Glance
- 2. Overview
- 3. Key Changes
- 3.1. Security Vulnerability Fixes and Update Recommendation
- 3.2. Multi-Page Support and Live Presence in Notes
- 3.3. Enhanced Administrator Features (Session Inspection and API Key Management)
- 3.4. Faster Knowledge Base Processing and Search
- 3.5. Improved Chat Screen Usability and Input Bug Fixes
- 3.6. Support for ComfyUI Animated Images and Metrics Exclusion Settings
- 4. Hardware Requirements
- 5. How to Get It
- 6. Related Articles
- 7. What to Read Next
- 8. Sources
At a Glance
| Item | Value |
|---|---|
| Repository | open-webui/open-webui |
| Version | v0.12.5 |
| Published | 2026-10-29 |
| License | NOASSERTION |
| Source type | Primary source (the publisher itself) |
Values determined by this site’s code when the information was collected. Dates are JST.
Overview
Open WebUI v0.12.5 has been released. Open WebUI is a user-friendly, Python-based AI interface that supports Ollama, the OpenAI API, and other backends.
This version includes important security fixes, and the development team strongly recommends updating as soon as possible across all environments. In terms of features, numerous changes have been made to improve usability and performance, such as multi-page support for notes, expanded administrator analytics, and up to 10x faster knowledge base searches.
Key Changes
Security Vulnerability Fixes and Update Recommendation
This release includes important security fixes. Prompt updates are strongly recommended for all deployments to ensure secure operation. Detailed advisories regarding individual vulnerabilities are scheduled to be published as soon as CVE assignments are complete. Administrators should update to the latest version immediately.
Multi-Page Support and Live Presence in Notes
The notes feature has been expanded to allow the creation of multiple pages and sub-pages within a single note. Page tabs allow users to add, rename, reorder, delete, and link to pages, with models and search functions operating on a per-page basis. Additionally, a “Live presence" feature has been implemented, allowing users to see in real-time which page and position other users are working on within a note.
Enhanced Administrator Features (Session Inspection and API Key Management)
A “Sessions" tab has been added to the administrator analytics. When the environment variable ENABLE_ADMIN_CHAT_ACCESS is enabled, administrators can list token counts, response contents, errors, and processing times for each chat, filtered by model and token range. Furthermore, individual API keys can now be rotated or deleted from the user edit dialog.
Faster Knowledge Base Processing and Search
Various knowledge base commands (ls, cat, grep) and synchronization checks have been improved to retrieve lists without reading the full text of each file. This increases call speeds by up to 10x in large knowledge bases and significantly reduces memory consumption. In addition, embedding processing for large documents now defaults to batch processing in increments of 1,000 chunks (configurable via the RAG_EMBEDDING_BUFFER_SIZE environment variable), greatly reducing memory load.
Improved Chat Screen Usability and Input Bug Fixes
Chats can now be renamed directly from the menu next to the open chat title. For chats within folders owned by the user, titles can be changed even if created by another user. Additionally, a bug (present since v0.12.4) has been fixed where pressing the Backspace key during Japanese or other IME text input would commit the text or cause it to display redundantly.
Support for ComfyUI Animated Images and Metrics Exclusion Settings
Images generated from ComfyUI’s “Save Animated WEBP" and “Save Animated PNG" nodes are now displayed in animated format on the chat screen. Also, in OpenTelemetry metrics, specifying OTEL_PYTHON_FASTAPI_EXCLUDED_URLS or OTEL_PYTHON_EXCLUDED_URLS now allows health check requests like /health to be excluded from metrics measurement.
Hardware Requirements
This version improves the flexibility of integrating external models and configuring various embedding and optical character recognition models.
-
Mistral OCR Model Selection and Custom Parameter Settings
TheAdmin Settings > Documentsmanagement screen and theMISTRAL_OCR_PARAMSenvironment variable can now be used to specify the Mistral OCR model to use or send additional request options. This allows flexible handling of older OCR model versions or parameter settings required by Azure AI Foundry endpoints. -
Improved Support for Kokoro.js (Browser Audio Model)
When selecting “Kokoro.js (Browser)" in audio settings (Settings > Audio), a bug was fixed where the Read Aloud function would not correctly speak using the selected Kokoro voice. -
UI Settings for Embedding Model Prefixes
Query prefixes (RAG_EMBEDDING_QUERY_PREFIX) and content prefixes (RAG_EMBEDDING_CONTENT_PREFIX) required by certain embedding models can now be configured directly from theAdmin Settings > Documentsmanagement screen, in addition to the traditional environment variable configuration. -
Support for Reranker Models Returning Negative Scores
When using reranker models that return raw scores below 0, negative values can now be entered into the Relevance Threshold field underAdmin Settings > Documents. -
Nvidia GPU / CUDA Acceleration
In Docker environments, acceleration using Nvidia GPUs is available by using CUDA-enabled images (ghcr.io/open-webui/open-webui:cuda) or GPU flags.
How to Get It
Open WebUI installation and updates are performed using Python pip or Docker. Follow the steps below according to your existing environment.
Python pip Updates and Installation
To avoid compatibility issues, Python 3.12 is recommended.
- Install or update the package:
pip install open-webui
- Start the server:
open-webui serve
After starting, access http://localhost:8080 in your browser to use it.
Docker Updates and Installation
When operating with Docker, be sure to run the container with the data mount option -v open-webui:/app/backend/data specified to prevent data loss.
- When Ollama is running on the same machine
docker run -d -p 3000:8080 --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
- When Ollama is running on another server
Specify the target server’s URL inOLLAMA_BASE_URL.
docker run -d -p 3000:8080 -e OLLAMA_BASE_URL=https://example.com -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
- When using Nvidia GPU (CUDA)
Install the Nvidia CUDA container toolkit on your Linux or WSL environment beforehand, then run:
docker run -d -p 3000:8080 --gpus all --add-host=host.docker.internal:host-gateway -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:cuda
- When using only the OpenAI API
docker run -d -p 3000:8080 -e OPENAI_API_KEY=your_secret_key -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:main
- When using the bundled image containing both Open WebUI and Ollama
- With GPU support:
bash docker run -d -p 3000:8080 --gpus=all -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama– CPU only:bash docker run -d -p 3000:8080 -v ollama:/root/.ollama -v open-webui:/app/backend/data --name open-webui --restart always ghcr.io/open-webui/open-webui:ollama
When started via Docker, access http://localhost:3000.
Related Articles
- Open WebUI v0.13.0 Released: Tabbed Workspaces & Security Fixes
- Open WebUI v0.12.0 Released: Real-Time Voice & VRM Avatars
- Open WebUI v0.11.4 Released: Dramatic Docker Image Slimming
- Open WebUI v0.13.1 Released with Security Fixes and Tether
What to Read Next
- Follow this tool → Open WebUI overview and release history (181 releases tracked)
- Other uis and desktop apps → Jan / TextGen
- Engines mentioned in this article → Ollama
Sources
- open-webui/open-webui v0.12.5 Release Notes
- Pull Request #33177: feat: rename a chat from the menu next to its title
- Pull Request #33339: fix: folder owners can rename another user’s chat from the menu next to its title
- Pull Request #33329: feat: let admins exclude routes like health checks from OpenTelemetry metrics
- Pull Request #33183: fix: the search window only offers locations that fit the chosen content type

