On March 31, Web3 security firm CertiK released the "OpenClaw Security Report," providing a systematic review and analysis of the security boundaries and risk patterns that emerged during OpenClaw's development, along with protection recommendations for both developers and users.
The report points out that OpenClaw's architecture connects external inputs with a local high-privilege execution environment. This "high capability + high privilege" design enhances automation but also imposes greater security demands: its early security model, based on a "local trusted environment," gradually revealed limitations in complex deployment scenarios. Data shows that between November 2025 and March 2026, OpenClaw accumulated over 280 GitHub security advisories and more than 100 CVE vulnerabilities. The research summarizes typical risk types and their root causes across multiple layers, including gateway control, identity binding, execution mechanisms, and the plugin ecosystem.
Building on this, the report offers key recommendations for developers and users: Developers need to establish threat models early, incorporating access control, sandbox isolation, and privilege inheritance mechanisms into the core design. They should also strengthen validation and constraints for plugins and external inputs. Users should avoid public network exposure, implement the principle of least privilege, and continuously conduct configuration audits and environment isolation management to mitigate the risks of system abuse or misuse.