CVE-2026-110689 in ClawScan
Summary
by MITRE • 10/14/2026
A security flaw has been discovered in OpenClaw ClawScan up to 0.1.6. This impacts the function shouldSkipTargetPath of the file internal/runner/runner.go of the component Static Scanner. Performing a manipulation results in protection mechanism failure. Attacking locally is a requirement. The exploit has been released to the public and may be used for attacks. Upgrading to version 0.1.7 will fix this issue. The patch is named 9f6a6fbb9f1137345566d0ab44c73893dfe112fa. The affected component should be upgraded.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/14/2026
A critical security vulnerability has been identified within the OpenClaw ClawScan utility, specifically affecting versions up to 0.1.6. This flaw resides in the Static Scanner component and centers on a logic error within the internal/runner/runner.go file. The specific function compromised is shouldSkipTargetPath, which is responsible for determining whether certain target paths should be excluded from scanning operations based on predefined security policies or exclusion rules. The nature of this defect constitutes a failure in access control mechanisms where the software incorrectly evaluates path constraints, leading to a bypass of intended protection measures. This type of vulnerability aligns with CWE-284 Improper Access Control and more specifically CWE-732 Incorrect Permission Assignment for Critical Resource when considering how file system paths are handled during security scans.
The operational impact of this flaw is significant because it allows an attacker who has local access to the system where ClawScan is deployed to manipulate input parameters or environment variables in a way that causes the shouldSkipTargetPath function to return incorrect results. By exploiting this logic error, an adversary can force the scanner to skip critical directories or files that were intended to be protected and analyzed. This protection mechanism failure effectively blinds the security tool to specific areas of the system, allowing malicious activities such as data exfiltration, persistence establishment, or lateral movement to go undetected by the static analysis process. Since local access is a prerequisite for exploitation, this vulnerability poses a severe risk in environments where untrusted users have shell access but are expected to be restricted from accessing sensitive configuration files or system binaries that ClawScan is supposed to monitor.
The existence of publicly released exploit code further elevates the severity of this issue by lowering the barrier to entry for attackers. Once an attacker achieves local foothold, they can leverage these public exploits to reliably bypass the scanning protections without needing to develop custom tooling. This scenario maps directly to MITRE ATT&CK techniques related to Defense Evasion, particularly T1562 Impair Defenses or T1070 Indicator Removal on Host if the goal is to hide malicious artifacts from detection systems that rely on ClawScan outputs. The ability to disable specific scan targets means that subsequent security assessments may yield false negatives, giving a false sense of security while actual threats remain active and undetected within the skipped paths.
To mitigate this risk, organizations running OpenClaw ClawScan must immediately upgrade to version 0.1.7 or any later release where the patch identified as commit hash 9f6a6fbb9f1137345566d0ab44c73893dfe112fa has been integrated. This update corrects the logic within the shouldSkipTargetPath function to ensure that path exclusion rules are applied strictly and securely, preventing unauthorized bypasses. In addition to upgrading, administrators should audit system access controls to limit local user privileges where possible, reducing the attack surface for initial exploitation. Regular monitoring of ClawScan logs for anomalies in skipped paths can also help detect potential attempts to exploit this vulnerability before a full patch is deployed across all systems.