← Back to Scanner

open-webui Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

open-webui is an AI agent skill, created by open-webui and published at open-webui/open-webui. ClawSecure audited open-webui across 111 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 35/100 (High Risk). The 7 findings concentrate in Code Injection and Permissions Manifest, including Potentially dangerous code pattern detected: base64.*decode and Potentially dangerous code pattern detected: base64.*decode. 6 were rated high or critical severity.

Is open-webui safe?

ClawSecure audited open-webui and assigned a security score of 35/100 (High Risk), identifying 7 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in open-webui?

ClawSecure identified 7 findings in open-webui, concentrated in Code Injection and Permissions Manifest. 6 were rated high or critical severity. The most severe include Potentially dangerous code pattern detected: base64.*decode and Potentially dangerous code pattern detected: base64.*decode.

How was open-webui audited?

ClawSecure ran open-webui through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 111 files from open-webui/open-webui.

What does a score of 35 mean?

ClawSecure assigned open-webui a security score of 35/100, placing it in the High Risk range. This is driven by 7 findings led by Code Injection that should be addressed before use. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for open-webui

ClawSecure detected 7 security findings in open-webui, spanning Code Injection and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for open-webui

Eliminate dynamic code execution
open-webui evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent SecurityBeyond Static Scans: Why ClawSecure Verifies Agentic Intent

Related AI Agent Security Audits

openclawScore 45/100fzfScore 25/100gnoScore 45/100keepScore 45/100ClawSecScore 45/100

Scanned on July 27, 2026. open-webui is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan