CVE-2026-101882 in Windows
Summary
by MITRE • 09/30/2026
OpenClaw Windows Node before 2026.7.1 contains an incomplete validation vulnerability in system.execApprovals.set that accepts wildcard-executable rules and abusable system binaries like mshta, rundll32, and certutil. Remote callers can add broad allow rules to execute arbitrary commands on the Windows host through system.run without operator checks or user prompts.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Analysis
by VulDB Data Team • 09/30/2026
The vulnerability identified in OpenClaw Windows Node versions prior to 2026.7.1 represents a critical failure in input validation and access control mechanisms within the application's execution approval subsystem. Specifically, the flaw resides in the system.execApprovals.set function, which is designed to manage rules governing executable permissions on the host machine. The core technical deficiency lies in the incomplete validation of rule parameters, allowing remote callers to inject wildcard-executable patterns that are excessively broad and permissive. This lack of granular restriction enables the creation of allow rules that effectively bypass intended security boundaries, granting unauthorized execution privileges for arbitrary commands without requiring operator approval or user interaction prompts.
From a technical perspective, this vulnerability exploits the application's trust model regarding command execution policies. By accepting wildcard patterns, the system fails to enforce strict path validation or binary whitelisting practices necessary for secure operation on Windows environments. The attacker can leverage well-known legitimate system binaries such as mshta.exe, rundll32.exe, and certutil.exe, which are commonly included in default allow lists due to their utility by administrators. These utilities are frequently abused in living-off-the-land attacks because they possess the capability to download files, execute scripts, or decode data without triggering standard security alerts when invoked through improperly configured execution policies. The absence of operator checks means that once these rules are applied via system.run, any subsequent command invocation matching the broad criteria is automatically permitted, effectively neutralizing a key layer of defense against unauthorized code execution.
The operational impact of this vulnerability is severe, as it allows for remote code execution with potentially elevated privileges depending on the context in which OpenClaw runs. An attacker who can interact with the system.execApprovals.set interface can establish persistent backdoors or facilitate lateral movement by executing malicious payloads disguised as legitimate administrative tasks. This capability undermines the integrity of the host operating system, enabling data exfiltration, credential theft, and further compromise of connected network resources. The vulnerability aligns closely with CWE-20 Improper Input Validation, where insufficient sanitization allows attackers to inject harmful inputs that alter program flow or permissions. Furthermore, it maps to MITRE ATT&CK techniques such as T1059 Command and Scripting Interpreter for the abuse of system utilities and T1084 Remote Services if exploited over network interfaces, highlighting its relevance in modern threat landscapes involving living-off-the-land binaries.
Mitigation strategies must prioritize immediate patching to version 2026.7.1 or later where these validation checks have been hardened. In the interim, administrators should implement strict firewall rules to restrict access to OpenClaw management interfaces from untrusted networks and enforce principle of least privilege by limiting which users can modify execution approval policies. Additionally, deploying endpoint detection and response solutions that monitor for unusual invocations of mshta, rundll32, or certutil in non-standard contexts can provide compensating controls against exploitation attempts. Regular auditing of system.execApprovals configurations is also recommended to ensure no overly permissive wildcard rules exist within the environment.