PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-44567 open-webui CVE debrief

Open WebUI versions prior to 0.1.124 contain an authorization bypass vulnerability where the API fails to validate that a user possesses an authorized role of 'user'. When new sign-ups are enabled, the default user role is set to 'pending', requiring administrator intervention to assign proper access. Due to insufficient server-side authorization checks, pending users can access API endpoints and functionality intended only for authorized users, bypassing the intended access control workflow. This vulnerability is classified under CWE-602 (Server-Side Request Forgery) and CWE-863 (Incorrect Authorization) per the vendor advisory. The issue was resolved in version 0.1.124 with proper role validation enforcement.

Vendor
open-webui
Product
Unknown
CVSS
HIGH 7.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-05-15
Original CVE updated
2026-05-19
Advisory published
2026-05-15
Advisory updated
2026-05-19

Who should care

Organizations running self-hosted Open WebUI instances with public or semi-public sign-up enabled, particularly those relying on the pending approval workflow for access control. Security teams responsible for AI/ML platform governance and compliance officers managing data access controls in offline AI deployments.

Technical summary

The vulnerability stems from missing server-side authorization checks in Open WebUI's API layer. When DEFAULT_USER_ROLE is set to 'pending' (the default when ENABLE_SIGNUP=true), new registrations receive pending status pending administrator approval. However, the API endpoints fail to verify the user's current role before processing requests, allowing pending users to invoke functionality reserved for user or admin roles. This represents a classic insecure direct object reference and missing function-level access control pattern. The fix in 0.1.124 implements proper role validation middleware across protected API routes.

Defensive priority

HIGH

Recommended defensive actions

  • Upgrade Open WebUI to version 0.1.124 or later to remediate the authorization bypass vulnerability.
  • If immediate patching is not feasible, disable new user sign-ups or implement additional network-level access controls to restrict pending users from accessing API endpoints.
  • Review user role assignments in the Admin management panel to ensure no pending users have gained unauthorized access prior to remediation.
  • Monitor API access logs for anomalous activity from users with pending role status.

Evidence notes

Vendor advisory confirms the vulnerability exists in versions prior to 0.1.124, with fix implemented in that version. CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L indicates network attack vector with low attack complexity, no privileges required, and low impacts across confidentiality, integrity, and availability.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-44567 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-44567

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-44567 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44567

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.