Quick answers
- Is CVE-2026-109297 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109297 being exploited in the wild.
- How severe is CVE-2026-109297?
- Medium severity, with a CVSS score of 6.5, published 12 October 2026.
- Which products and versions are affected?
- Open WebUI 0.11.0 through 0.11.3.
- Is there a fix for CVE-2026-109297?
- Yes: fixed in 0.11.4. Until then: Restrict the USER_PERMISSIONS_FEATURES_AUTOMATIONS setting to administrators only, which is the default. Ensure UVICORN_WORKERS is set to more than 1 to allow other workers to remain responsive during validation operations. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109297 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-109297?
- Check whether you run Open WebUI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.11.4
Restrict the USER_PERMISSIONS_FEATURES_AUTOMATIONS setting to administrators only, which is the default. Ensure UVICORN_WORKERS is set to more than 1 to allow other workers to remain responsive during validation operations.
Technical details
The recurrence-rule validator in backend/open_webui/utils/automations.py parses rules differently than the underlying calendar library, allowing attackers to submit rules that appear benign to the validator but expand to per-second schedules when executed. Validation and scheduler polling synchronously walk every occurrence from the rule's start date to present on the shared event loop without timeout, consuming CPU for minutes and blocking all other operations. Authentication and automation creation permissions are required; this is available to non-administrators only when the automations feature is explicitly granted.
Affected products
- Open WebUI Open WebUI 0.11.0 through 0.11.3
Timeline
- 2026-09-27: disclosed
- 2026-10-12: advisory
- 2026-10-12: patched