Open WebUI 0.12: security fixes, two-factor sign-in, Ollama fixes

Open WebUI released v0.12.0 on Oct 10, 2026. It includes security and access-control fixes, and the project recommends updating production deployments at the earliest convenience. Not all security fixes may be listed. Some may be withheld for a short time so administrators can upgrade first. v0.12.0 adds two-factor sign-in. Administrators can require an authenticator app for every user under Admin Settings > Authentication or with `ENABLE_MFA`. Each user gets ten single-use recovery codes. It also fixes several Ollama issues. A `max_tokens` value sent through the API now limits Ollama replies; before, Ollama ignored it. An Ollama connection's custom headers, authentication type and cookie forwarding now apply to every request, including loading, downloading and unloading models. Cancelling an Ollama download no longer deletes an existing copy of the model. GGUF uploads in Manage Ollama now create the model. Unloading a model from Ollama or llama.cpp refreshes the model list right away. JSON is now handled with orjson by default; the notes say live socket updates encode about 17 times and decode about 3 times faster. v0.12.1 (Oct 14) includes database schema changes. The project strongly recommends backing up before upgrading in production. Multi-worker, multi-server or load-balanced deployments must update all instances at the same time; rolling updates are not supported. v0.12.2 (Oct 14) fixes advisory GHSA-3vvh-g22g-jq6r (medium, published Oct 18): a channel member could post messages shown as coming from a channel webhook. v0.12.3 (Oct 16) adds temporary end-to-end encrypted chats in direct messages and private group channels. Messages up to 16 KiB are encrypted in the browser with MLS and passed through the server without being saved. An administrator must enable it with `ENABLE_ENCRYPTED_CHANNELS` or in Admin Settings and grant the permission. The Google Drive picker now asks only for access to the files a user picks.