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-109297 Overview
CVE-2026-109297 is a denial of service vulnerability in Open WebUI versions 0.11.0 through 0.11.3. The flaw resides in the automation recurrence-rule validator, which parses rule text more strictly than the calendar library that later executes those rules. Authenticated users with permission to create automations can submit crafted recurrence rules that expand per-second synchronously. Each malicious rule blocks the shared event loop for minutes per request and repeats on every scheduler poll. The weakness is classified as CWE-400: Uncontrolled Resource Consumption.
Critical Impact
A single authenticated low-privilege user can stall the Open WebUI event loop for minutes, degrading availability for all tenants and recurring on every scheduler cycle.
Affected Products
- Open WebUI 0.11.0
- Open WebUI 0.11.1 through 0.11.3
- Fixed in Open WebUI 0.11.4
Discovery Timeline
- 2026-10-12 - CVE-2026-109297 published to the National Vulnerability Database
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-109297
Vulnerability Analysis
Open WebUI validates automation recurrence rules (RRULEs) before persisting them. The validator enforces constraints intended to block sub-daily frequencies, which would otherwise produce an unbounded number of occurrences. The guard parses rule text using strict tokenization rules. The downstream calendar library that actually expands the rule applies looser parsing semantics.
This parser mismatch creates a bypass. An attacker crafts a rule that the validator reads as benign but that the executing library interprets as a per-second frequency. When the automation scheduler polls the rule, it synchronously enumerates occurrences, consuming CPU and blocking the asynchronous event loop that serves all other HTTP and WebSocket traffic.
Root Cause
The sub-daily frequency guard performs strict textual checks that diverge from the lenient parser used at execution time. In version 0.11.0, the guard additionally fails to normalize lowercase frequency tokens and does not require the RRULE: prefix. Whitespace-folded rules bypass validation across the entire affected range. The underlying problem is inconsistent input validation between two parsers acting on the same data.
Attack Vector
Exploitation requires an authenticated account with permission to create automations. The attacker submits a recurrence rule that uses whitespace folding, lowercase frequency identifiers, or a missing RRULE: prefix to evade the validator. Once stored, the scheduler polls the automation on its normal interval. Each poll triggers synchronous per-second expansion that monopolizes the event loop for minutes. The attack vector is network-based and requires no user interaction beyond initial authentication.
Technical details are documented in the GitHub Security Advisory GHSA-whgc-vpjx-m3qh and the VulnCheck Advisory on DoS.
Detection Methods for CVE-2026-109297
Indicators of Compromise
- Automation definitions containing recurrence rules with unusual whitespace folding, lowercase frequency tokens such as freq=secondly, or missing RRULE: prefixes.
- Prolonged event loop stalls in Open WebUI logs, visible as request timeouts or scheduler poll durations lasting minutes.
- Sustained single-core CPU saturation on the Open WebUI process coinciding with scheduler intervals.
Detection Strategies
- Audit the automations table for recently created or modified recurrence rules and flag any that do not match a normalized RRULE: pattern with uppercase keywords.
- Correlate scheduler poll timestamps with CPU spikes and HTTP latency increases to identify abusive rules.
- Monitor authenticated user activity for accounts that create automations outside normal operational baselines.
Monitoring Recommendations
- Export Open WebUI application logs to a centralized logging platform and alert on event loop blocking warnings.
- Instrument the Python process with metrics on request duration, scheduler job runtime, and CPU utilization per worker.
- Track automation creation events per user and alert when creation rate or rule complexity exceeds a defined threshold.
How to Mitigate CVE-2026-109297
Immediate Actions Required
- Upgrade Open WebUI to version 0.11.4 or later, which aligns validator and executor parsing semantics.
- Review all existing automation recurrence rules and delete any that use sub-daily frequencies or non-standard formatting.
- Restrict automation creation permissions to trusted operators until the upgrade is complete.
Patch Information
The fix is included in Open WebUI 0.11.4. The upgrade tightens the recurrence-rule validator to match the lenient parsing used by the calendar library, closing the whitespace, case, and prefix bypass paths. Review the GitHub Security Advisory GHSA-whgc-vpjx-m3qh for release notes and verification steps.
Workarounds
- Temporarily disable the automations feature or the scheduler worker if an immediate upgrade is not feasible.
- Enforce a pre-insertion server-side filter that rejects any recurrence rule not matching a strict, uppercase, prefixed RRULE grammar.
- Place Open WebUI behind a reverse proxy that rate-limits automation creation endpoints per authenticated user.
# Verify running version and upgrade
docker inspect open-webui --format '{{.Config.Image}}'
docker pull ghcr.io/open-webui/open-webui:0.11.4
docker stop open-webui && docker rm open-webui
docker run -d --name open-webui -p 3000:8080 ghcr.io/open-webui/open-webui:0.11.4
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

