Open WebUI, one of the most widely deployed self-hosted LLM front ends, published v0.11.2 on 31 August at 05:48:23 UTC. The notes carry an explicit statement of policy: security advisories for the release may be withheld for a short time to give administrators time to upgrade.
The policy, stated plainly
Delayed disclosure is a real and legitimate practice. Give defenders a head start; publish details once the patch has propagated. Open WebUI deserves credit for writing the policy down rather than doing it silently, which is the more common behaviour. But the trade-off deserves stating too, because it is not symmetric in the way the phrasing implies.
Who the delay actually helps
The window does not hide the fix. This is an open-source project: the commits are public the moment the release is. Anyone motivated can diff two tags and locate the patched code path in minutes — that is the standard route from patch to working exploit, and it is unaffected by whether an advisory has been filed. What the delay withholds is the severity and the class of the issue, and it withholds those from the administrator deciding whether this upgrade goes in tonight or at the end of the sprint. The attacker reads the diff. The defender reads "at your earliest convenience."
The pattern before it
The prior release, v0.11.1, shipped on 25 August at 21:17:57 UTC. Its security advisories were published roughly five days later, on 30 August. So the gap is not hypothetical, and v0.11.2 now sits in the same state its predecessor was in — carrying undisclosed security content while operators are asked to trust the instruction rather than the detail.
What the common framing gets wrong
Changelog summaries file these releases as maintenance, because that is what they read like: a list of bug fixes in the same register as UI tweaks. A reader scanning for "security" finds nothing to prioritise. The severity information exists, the project has it, and the interval in which it is withheld is precisely the interval in which the upgrade decision is made.
The practical reading
For a self-hosted deployment exposed to more than one user, treat any Open WebUI release carrying this notice as security-relevant by default and schedule it accordingly. The absence of a published advisory is not evidence that there is nothing to patch — the notes say as much.