CVE-2026-28460: Medium Vulnerability in OpenClaw

OpenClaw versions prior to 2026.2.22 contain an allowlist bypass vulnerability in system.run that allows attackers to execute non-allowlisted commands by splitting command substitution using shell line-continuation characters. This vulnerability allows attackers to bypass security analysis by injecting $\\ followed by a newline and opening parenthesis inside double quotes, causing the shell to fold the line continuation into executable command substitution that circumvents approval boundaries.

The CVSS score for this vulnerability is 6, indicating a medium severity level. Organizations should prioritize patching immediately, as the risk to organizations includes unauthorized command execution that can lead to integrity violations.

Currently, there is no known public exploit available, and this vulnerability is not listed in the KEV catalog. However, the potential for exploitation through network access with low attack complexity makes it imperative for defenders to take swift action.

Organizations should schedule remediation to address this vulnerability in their security practices and ensure that proper measures are in place to validate command executions.

Vulnerability Details

The official CVE description states that OpenClaw's allowlist bypass vulnerability can lead to unauthorized command execution. The affected product is OpenClaw, with a CVSS score of 6, categorized as medium severity due to the potential for high integrity impact and low availability impact.

This vulnerability was published on March 19, 2026, with the last modification on March 25, 2026. It is classified under CWE-78, indicating a command injection vulnerability.

Technical Analysis

The root cause of this vulnerability stems from improper command handling in the system.run function of OpenClaw. Attackers can leverage shell line-continuation characters to execute commands that are not allowed by the system's security policies.

The attack vector is network-based, with low complexity required for exploitation. Attackers require low privileges and no user interaction is necessary to exploit this vulnerability. The confidentiality impact is none, while integrity impact is high, and availability impact is low.

Risk & Impact Analysis

The real-world deployment risk associated with this vulnerability is significant, as attackers may leverage this flaw to gain unauthorized access to sensitive commands, leading to potential data breaches or system integrity violations. Given the nature of the vulnerability, organizations may face a wide blast radius if exploited.

Organizations should address this vulnerability in their priority patch cycle to mitigate the risk of exploitation. The combination of low complexity and the ability to execute impactful commands makes this vulnerability a high priority for remediation.

Affected Versions

All versions of OpenClaw prior to 2026.2.22 are affected by this vulnerability. Organizations should ensure they upgrade to the latest version to mitigate this risk.

Mitigation & Remediation

Organizations should prioritize patching to version 2026.2.22 or later to remediate this vulnerability. If a patch is unavailable, organizations are advised to implement strict controls on command execution and conduct thorough security assessments to prevent exploitation.

For further guidance on securing your applications, refer to our application security assessment services.

Detection Guidance

Organizations should monitor logs for unusual command executions and system changes. Behavioral anomalies related to command execution in the system.run function should be flagged for review.

AppSecure Threat Intelligence Insight

This vulnerability highlights the importance of securing command execution environments. Security teams should consider implementing robust input validation and command approval mechanisms to prevent similar vulnerabilities in the future.

For strategic insights into vulnerability management, refer to our guide on vulnerability management and consider adopting best practices from our penetration testing methodology article.

Additionally, organizations should stay informed about emerging threats and vulnerabilities by consulting our red teaming guide for comprehensive threat intelligence.