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

CVE-2026-109298: Open WebUI DOS Vulnerability

CVE-2026-109298 is a denial of service vulnerability in Open WebUI versions 0.11.0 to 0.11.3. Authenticated attackers can exploit regex patterns to block the event loop and exhaust memory. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

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-109298 Overview

CVE-2026-109298 affects Open WebUI versions 0.11.0 through 0.11.3. The flaw lives in the knowledge and chat file search tools, which compile user-chosen grep patterns with a regex engine that expands nested counted repetition unbounded at compile time and caches the result. Authenticated users can direct the model to call grep_knowledge_files with short nested-repetition patterns. These patterns block the asyncio event loop and exhaust worker memory, degrading or halting the service for all users. The weakness is classified as uncontrolled resource consumption [CWE-400].

Critical Impact

Any authenticated user can trigger worker memory exhaustion and event-loop blockage with a short crafted regex, producing a denial-of-service condition against the Open WebUI backend.

Affected Products

  • Open WebUI 0.11.0
  • Open WebUI versions after 0.11.0 and before 0.11.4
  • Open WebUI knowledge and chat file search tools (grep_knowledge_files)

Discovery Timeline

  • 2026-10-12 - CVE-2026-109298 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-109298

Vulnerability Analysis

Open WebUI exposes file search tools that LLM agents can invoke on behalf of authenticated users. The grep_knowledge_files and chat file search tools accept arbitrary regex patterns from the model's tool call. Those patterns are compiled with the third-party regex Python module, which supports features such as nested counted repetition and performs significant work at compile time. Compiled patterns are then cached, meaning the compile-time cost is paid again for each new malicious pattern.

A short nested-repetition pattern such as (a{10}){10}{10} forces the engine to expand the counted repetitions during compilation. This expansion grows super-linearly with the depth and width of the nesting. Because Open WebUI runs tool calls on the main asyncio event loop, a single long compilation blocks all concurrent requests. Repeated calls further grow memory and can crash the worker process.

Root Cause

The root cause is the use of a regex engine that permits unbounded compile-time expansion of nested counted repetition combined with the absence of pattern validation, timeout, or complexity limits on model-controlled inputs. The vulnerable code imports the regex library inside backend/open_webui/tools/knowledge_fs.py and relies on its cache without constraining input shape.

Attack Vector

An authenticated user instructs the model to invoke grep_knowledge_files with a crafted nested-repetition pattern. The backend compiles the pattern on the event loop, consumes CPU and memory, and stops serving other requests. No privileged role is required beyond standard authenticated access.

python
# Patch excerpt - backend/open_webui/tools/knowledge_fs.py
 from contextlib import contextmanager
 from typing import Optional

-import regex
+import re2
 from fastapi import Request

 from open_webui.env import (
python
# Patch excerpt - backend/open_webui/tools/builtin.py
     """
     Search exact text across files attached to the current chat.
     Pass file_id from the attached_files block to search one file.
+    Auto-detected regex uses RE2 syntax; no lookarounds/backreferences, and shorthand classes are ASCII-only.

     :param pattern: The text pattern to search for
     :param file_id: Optional attached file ID to search within a single file

Source: Open WebUI patch commit 97e013a

Detection Methods for CVE-2026-109298

Indicators of Compromise

  • Spikes in Open WebUI worker memory usage correlated with tool calls to grep_knowledge_files or the chat file search tool.
  • Event-loop stalls, request timeouts, or health-check failures on the Open WebUI backend during normal user activity.
  • Audit logs showing authenticated users submitting prompts containing nested counted repetition patterns such as (a{N}){M}.

Detection Strategies

  • Parse Open WebUI application logs for tool invocations where the pattern parameter contains nested {n} quantifiers or very short strings that compile into large automata.
  • Correlate container or process metrics (RSS growth, CPU saturation on a single worker) with the timestamp of search tool calls.
  • Alert on repeated worker restarts or OOM-kill events on hosts running Open WebUI 0.11.0 through 0.11.3.

Monitoring Recommendations

  • Enable per-user rate limiting and audit logging on tool calls, and retain the raw pattern argument for forensic review.
  • Monitor Python process memory and event-loop latency with an APM agent to catch compile-time stalls early.
  • Track Open WebUI version inventory across environments to confirm no vulnerable 0.11.0–0.11.3 instances remain in production.

How to Mitigate CVE-2026-109298

Immediate Actions Required

  • Upgrade Open WebUI to version 0.11.4 or later, which replaces the regex module with re2 in file search tools.
  • Restrict access to the knowledge and chat file search features to trusted authenticated users until the upgrade is applied.
  • Place the Open WebUI backend behind a reverse proxy that enforces request timeouts and per-user rate limits.

Patch Information

The fix is implemented in commit 97e013a66169c4fcd7f26ab9e41a4ff260ffd4da and shipped in Open WebUI 0.11.4. The patch swaps the vulnerable regex import for Google's re2 engine in backend/open_webui/tools/knowledge_fs.py and documents that auto-detected regex uses RE2 syntax with no lookarounds, no backreferences, and ASCII-only shorthand classes. RE2 guarantees linear-time matching and bounded compilation, which removes the compile-time expansion primitive. See the GitHub Security Advisory GHSA-gww9-mhgj-pfqh and the VulnCheck advisory for additional context.

Workarounds

  • Disable the grep_knowledge_files and chat file search tools in Open WebUI tool configuration until patching is complete.
  • Enforce container memory limits and automatic restart policies so that a single exhausted worker does not take down the deployment.
  • Add an upstream input filter that rejects tool-call payloads containing nested counted repetition such as (.{\d+}){\d+}.
bash
# Upgrade Open WebUI via pip
pip install --upgrade "open-webui>=0.11.4"

# Or pull the patched container 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 \
  --memory=2g --memory-swap=2g --restart=on-failure \
  -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

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.