Open WebUI load_tool_module_by_id कमांड इंजेक्शन रिमोट कोड एग्जीक्यूशन भेद्यता

An attacker exploiting CVE-2026-0766 can execute arbitrary code on the affected Open WebUI instance. Given that Open WebUI is often used for managing network devices, this could lead to complete control over those devices. Attackers could potentially modify configurations, steal sensitive data (credentials, device settings), or use the compromised device as a pivot point to attack other systems on the network. The ability to execute code in the context of the service account amplifies the potential damage, as this account may have elevated privileges. This vulnerability shares similarities with command injection flaws where untrusted input is directly incorporated into system commands.

Organizations utilizing Open WebUI for network device management are at risk, particularly those relying on version 0.6.32. Shared hosting environments where multiple users share the same Open WebUI instance are also vulnerable, as a compromised account could be used to exploit the vulnerability and gain access to other users' devices. Legacy configurations with default credentials or weak access controls further exacerbate the risk.

• linux / server:

journalctl -u openwebui -g 'load_tool_module_by_id'

• generic web:

curl -I http://<openwebui_ip>/api/v1/tools/load_tool_module_by_id?module_id=<suspicious_input>

• generic web: Grep access/error logs for requests containing suspicious characters or patterns within the module_id parameter. Look for unusual Python code execution attempts.

1. 2026-01-23Disclosure

   disclosure

1. आरक्षित2026-01-08
2. प्रकाशित2026-01-23
3. संशोधित2026-02-26
4. EPSS अद्यतन2026-03-23

The primary mitigation for CVE-2026-0766 is to upgrade to a patched version of Open WebUI as soon as it becomes available. Until a patch is released, restrict access to the Open WebUI interface to only trusted users and networks. Implement strict input validation on all user-supplied data within the loadtoolmodulebyid function as a temporary workaround, although this requires significant code modification. Monitor system logs and network traffic for any suspicious activity, particularly attempts to execute unusual commands or access sensitive files. Consider implementing a Web Application Firewall (WAF) to filter potentially malicious requests. After upgrade, confirm functionality by testing key features and verifying that the loadtoolmodulebyid function no longer accepts arbitrary code execution.