Skip to main content
Vulnerability Database/CVE-2026-109299

CVE-2026-109299: Open WebUI Denial of Service Vulnerability

CVE-2026-109299 is a denial of service vulnerability in Open WebUI that allows authenticated users to stall instances through unsatisfiable recurrence rules. This post explains its technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-109299 Overview

CVE-2026-109299 is a denial of service vulnerability in Open WebUI versions 0.9.0 through 0.11.3. Authenticated users with the automations permission can stall the application by submitting unsatisfiable recurrence rules to the automations create or update endpoints. Each malformed rule, such as one referencing February 30th, blocks the shared event loop for several seconds while the backend attempts to evaluate it. Repeated submissions amplify the impact and starve legitimate requests of processing time. The flaw is tracked under [CWE-400: Uncontrolled Resource Consumption].

Critical Impact

Low-privileged authenticated users can repeatedly stall the Open WebUI event loop, degrading or halting service availability for all tenants on the instance.

Affected Products

  • Open WebUI 0.9.0 through 0.11.3
  • Fixed in Open WebUI 0.11.4
  • Deployments exposing automations endpoints to authenticated users

Discovery Timeline

  • 2026-10-12 - CVE-2026-109299 published to the National Vulnerability Database
  • 2026-10-13 - Last updated in the NVD database

Technical Details for CVE-2026-109299

Vulnerability Analysis

Open WebUI exposes automations endpoints that accept recurrence rules describing when scheduled tasks should run. The backend evaluates these rules synchronously on the shared asyncio event loop. When an attacker submits a rule that can never match a real calendar date, the evaluator iterates searching for a next occurrence and blocks for seconds per request. Because the loop is shared across all HTTP handlers, every concurrent user experiences latency or request timeouts during the stall. Repeated submission to the create or update endpoints turns a single authenticated session into a reliable availability attack.

Root Cause

The automations subsystem lacked bounded evaluation of user-supplied recurrence rules. Input validation did not reject semantically impossible calendar expressions, and rule processing executed without a timeout or background worker isolation. Any CPU time spent walking the recurrence search space directly blocked the shared event loop handling other requests.

Attack Vector

Exploitation requires network access to the Open WebUI instance and valid credentials with automations permission. The attacker sends crafted JSON payloads to the automations create or update endpoints containing recurrence rules referencing non-existent dates such as February 30th. Each request consumes seconds of event loop time; a short loop of such requests is sufficient to render the instance unresponsive to other users.

python
# Patch excerpt: backend/open_webui/env.py introduces a bounded task TTL
 except ValueError:
     REDIS_RESPONSE_STREAM_TTL = 3600
 
+# Seconds a task survives without a heartbeat. 0 disables expiry.
+try:
+    REDIS_TASK_TTL = int(os.getenv('REDIS_TASK_TTL', '300'))
+    if REDIS_TASK_TTL != 0 and REDIS_TASK_TTL < 60:
+        REDIS_TASK_TTL = 300
+except ValueError:
+    REDIS_TASK_TTL = 300
+
 REDIS_SENTINEL_HOSTS = os.getenv('REDIS_SENTINEL_HOSTS', '')
 REDIS_SENTINEL_PORT = os.getenv('REDIS_SENTINEL_PORT', '26379')

Source: GitHub Commit 5fb869d

The fix also introduces a RecurrenceEvaluationTimeout exception in backend/open_webui/utils/recurrence.py to bound evaluation of user-supplied rules.

python
# Patch excerpt: backend/open_webui/main.py imports the new timeout type
     seed_registered_defaults,
 )
 from open_webui.constants import ERROR_MESSAGES, TASKS
+from open_webui.utils.recurrence import RecurrenceEvaluationTimeout
 from open_webui.env import (
     USE_SLIM,
     AIOHTTP_CLIENT_SESSION_SSL,

Source: GitHub Commit 5fb869d

Detection Methods for CVE-2026-109299

Indicators of Compromise

  • Repeated POST or PATCH requests from a single authenticated user to the Open WebUI automations create or update endpoints within short intervals.
  • Recurrence rule payloads referencing impossible calendar dates such as February 30th, February 31st, or April 31st.
  • Spikes in request latency and worker saturation on the Open WebUI backend without a corresponding increase in overall request volume.

Detection Strategies

  • Alert on bursts of automations create or update calls originating from the same session or API token.
  • Inspect request bodies for RRULE or recurrence fields with invalid BYMONTHDAY or BYDAY combinations that cannot resolve to a valid date.
  • Correlate sustained event loop stall telemetry with the identity of the authenticated user issuing automations requests.

Monitoring Recommendations

  • Capture application access logs for the automations endpoints and ship them to a centralized data lake for retention and query.
  • Monitor RecurrenceEvaluationTimeout exceptions after upgrading; these indicate blocked exploitation attempts.
  • Track per-user request rates and p99 response times for the automations API as a sustained performance signal.

How to Mitigate CVE-2026-109299

Immediate Actions Required

  • Upgrade Open WebUI to version 0.11.4 or later, which bounds recurrence rule evaluation.
  • Audit which accounts hold the automations permission and remove it from users who do not require scheduling capabilities.
  • Review recent automations create and update activity for recurrence rules containing impossible dates and remove suspicious entries.

Patch Information

The fix is delivered in commit 5fb869d and documented in GitHub Security Advisory GHSA-5w58-mwmh-vf2m. Additional analysis is available in the VulnCheck Advisory for Open WebUI. The patch introduces a RecurrenceEvaluationTimeout guard and a bounded REDIS_TASK_TTL environment variable to limit how long task state persists without a heartbeat.

Workarounds

  • Restrict the automations permission to a minimal set of trusted administrators until the upgrade is applied.
  • Place a reverse proxy rate limit in front of the automations create and update endpoints to cap requests per authenticated session.
  • Deploy a web application firewall rule that rejects recurrence payloads referencing invalid calendar days such as February 30th.
bash
# Example nginx rate limit for the automations endpoints
limit_req_zone $http_authorization zone=automations:10m rate=5r/m;

location ~ ^/api/v1/automations/ {
    limit_req zone=automations burst=5 nodelay;
    proxy_pass http://open_webui_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.