CVE-2026-44569

Open WebUI's Insecure Message Access Breaks Authorization

• Users can modify other users' message content within shared channels
• Read-only users gain write/delete capabilities over other users' content

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-44569 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.6.19); upgrading removes the vulnerable code path.

Kodem intelligence

Implement proper message ownership validation in the update and delete endpoints by adding ownership checks that follow the established security pattern used throughout the codebase. First, add a validation condition after the existing message retrieval to ensure only message owners or admins can modify messages: if user.role != "admin" and message.user_id != user.id and not has_access(user.id, type="write", access_control=channel.access_control) then raise a 403 Forbidden exception. Second, change the existing permission check from type="read" to type="write" for both update and delete operations to align with the access control model used in other routers (notes, prompts, knowledge, etc.).

1. What is CVE-2026-44569? CVE-2026-44569 is a high-severity missing authorization vulnerability in open-webui (pip), affecting versions <= 0.6.18. It is fixed in 0.6.19. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-44569? CVE-2026-44569 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of open-webui are affected by CVE-2026-44569? open-webui (pip) versions <= 0.6.18 is affected.
4. Is there a fix for CVE-2026-44569? Yes. CVE-2026-44569 is fixed in 0.6.19. Upgrade to this version or later.
5. Is CVE-2026-44569 exploitable, and should I be worried? Whether CVE-2026-44569 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-44569 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-44569? Upgrade open-webui to 0.6.19 or later.