https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 15:29:26 +0000 https://db.gcve.eu/vuln/bdu:2026-14837 bdu:2026-14837 https://db.gcve.eu/vuln/bdu:2026-14837 https://db.gcve.eu/vuln/fkie_cve-2026-87012 <p>Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.1, backend/open_webui/models/calendar.py stored the calendar event meta.alert_minutes value without type validation and the shared upcoming-event scheduler compared that value numerically. An authenticated user with the calendar permission could store a non-numeric alert_minutes value that raised an exception and aborted the instance-wide alert pass, suppressing all users&#39; reminders while the event remained in the lookahead window. This issue is fixed in version 0.11.1.</p> <p>Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.9.0 until 0.11.1, backend/open_webui/models/calendar.py stored the calendar event meta.alert_minutes value without type validation and the shared upcoming-event scheduler compared that value numerically. An authenticated user with the calendar permission could store a non-numeric alert_minutes value that raised an exception and aborted the instance-wide alert pass, suppressing all users&#39; reminders while the event remained in the lookahead window. This issue is fixed in version 0.11.1.</p> https://db.gcve.eu/vuln/fkie_cve-2026-87012 https://db.gcve.eu/vuln/ghsa-v39v-59xw-j98g <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Any authenticated user can suppress calendar alerts instance-wide via a non-numeric alert value</p> <p>## Summary</p> <p>Calendar events carry a free-form `meta` object that is stored exactly as submitted, with no validation of the values inside it. The scheduler reads the per-event alert offset out of that object in a single pass that covers every user&#39;s upcoming events, and compares it numerically without checking that it is a number. Any verified user could store a text value there, which made the comparison raise and abort the whole pass, so no calendar reminder fired for anyone on the instance while that event stayed inside the lookahead window.</p> <p>## Preconditions</p> <p>- Calendar is enabled (`ENABLE_CALENDAR` / `calendar.enable`, default `True`). - The attacker is a verified user (role `user` or `admin`) holding the `calendar` feature permission, which is granted to all users by default (`USER_PERMISSIONS_FEATURES_CALENDAR`, default `True`). - The event&#39;s start time falls inside the scheduler&#39;s one hour lookahead window, so the shared alert pass selects it.</p> <p>No admin access, no shared calendar, no recurrence rule and no open registration are required, an invited account is enough. Deployments running with the calendar disabled, or with the calendar feature permission removed from regular users, are not affected.</p> <p>## Impact</p> <p>Availability loss on one feature, affecting every user on the instance. While a single event carrying a non-numeric alert value sat in the upcoming window, the sha…</p> <p><strong>Affected:</strong> PyPI: open-webui</p> <p># Any authenticated user can suppress calendar alerts instance-wide via a non-numeric alert value</p> <p>## Summary</p> <p>Calendar events carry a free-form `meta` object that is stored exactly as submitted, with no validation of the values inside it. The scheduler reads the per-event alert offset out of that object in a single pass that covers every user&#39;s upcoming events, and compares it numerically without checking that it is a number. Any verified user could store a text value there, which made the comparison raise and abort the whole pass, so no calendar reminder fired for anyone on the instance while that event stayed inside the lookahead window.</p> <p>## Preconditions</p> <p>- Calendar is enabled (`ENABLE_CALENDAR` / `calendar.enable`, default `True`). - The attacker is a verified user (role `user` or `admin`) holding the `calendar` feature permission, which is granted to all users by default (`USER_PERMISSIONS_FEATURES_CALENDAR`, default `True`). - The event&#39;s start time falls inside the scheduler&#39;s one hour lookahead window, so the shared alert pass selects it.</p> <p>No admin access, no shared calendar, no recurrence rule and no open registration are required, an invited account is enough. Deployments running with the calendar disabled, or with the calendar feature permission removed from regular users, are not affected.</p> <p>## Impact</p> <p>Availability loss on one feature, affecting every user on the instance. While a single event carrying a non-numeric alert value sat in the upcoming window, the sha…</p> https://db.gcve.eu/vuln/ghsa-v39v-59xw-j98g