HIGH 7.1

CVE-2026-53865: OpenClaw Path Traversal in Maintenance Tasks (7.1 HIGH)

OpenClaw versions before 2026.5.2 contain a vulnerability that allows a local attacker with user-level access to execute arbitrary executables on the system. The flaw exists in how the maintenance task system handles file paths: an attacker can manipulate workspace-derived environment paths to trick the system into running their chosen command instead of the intended maintenance cleanup utility. This gives an attacker the ability to run code with the privileges of the OpenClaw process during routine maintenance operations.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.1 HIGH · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Weaknesses (CWE)
CWE-426
Affected products
3 configuration(s)
Published / Modified
2026-06-16 / 2026-06-18

NVD description (verbatim)

OpenClaw before 2026.5.2 contains a path traversal vulnerability in maintenance task execution that allows workspace-derived service paths to influence trash command selection. Attackers can execute unintended local executables from operator-unintended paths during maintenance operations by manipulating workspace-derived environment paths.

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-53865 is a path traversal vulnerability (CWE-426) in OpenClaw's maintenance task execution logic. The vulnerability arises from insufficient sanitization of workspace-derived service paths that influence trash command selection during maintenance operations. An attacker with local access can manipulate these environment-derived paths to achieve arbitrary local code execution. The CVSS 3.1 score of 7.1 (HIGH) reflects the local attack vector (AV:L), low attack complexity (AC:L), low privilege requirement (PR:L), and high impact on confidentiality and integrity, though availability is not compromised.

Business impact

This vulnerability poses a lateral privilege escalation and code execution risk within environments running OpenClaw maintenance operations. An attacker who gains initial local or unprivileged user access can leverage the maintenance scheduler to execute arbitrary code, potentially escalating their capabilities or maintaining persistence. Organizations relying on OpenClaw for workspace management should treat this as a containment boundary weakness: a compromised or malicious unprivileged user account can abuse maintenance windows to execute unvetted code, exfiltrate data, or modify system state. The impact is localized to the machine running OpenClaw but affects the integrity and confidentiality of data within that environment.

Affected systems

OpenClaw versions prior to 2026.5.2 are affected. Organizations running OpenClaw should verify their installed version immediately. The vulnerability requires local access and unprivileged user privileges to exploit, so it primarily affects multi-user systems or environments where unprivileged accounts have access to OpenClaw workspace directories.

Exploitability

Exploitation requires local access and low-level user privileges; it is not remotely exploitable. The attack is straightforward once access is obtained: an attacker manipulates workspace-derived environment paths before or during maintenance task execution to influence command resolution. No special tools or complex techniques are required beyond path manipulation. The low attack complexity and lack of user interaction requirements make this a practical threat in shared or compromised systems. However, the local privilege requirement and the requirement to interact with maintenance operations limit the immediate attack surface compared to remote vulnerabilities.

Remediation

Upgrade to OpenClaw version 2026.5.2 or later. This version contains fixes to properly sanitize workspace-derived paths and prevent them from influencing command selection during maintenance operations. After patching, verify that maintenance tasks execute cleanly and review any maintenance logs for signs of abnormal command execution during the window before patching.

Patch guidance

Apply version 2026.5.2 or any subsequent release as soon as possible. Prioritize patching on systems where OpenClaw maintenance runs with elevated privileges or in multi-user environments. Test the upgrade in a non-production environment first to ensure compatibility with your workspace configuration. Verify after patching that maintenance operations continue to function normally and that no workspace-specific customizations interfere with the path sanitization improvements.

Detection guidance

Monitor OpenClaw maintenance task execution logs for unexpected executable paths or commands that do not match known maintenance operations. Look for environment variable manipulation in process creation events tied to OpenClaw maintenance processes. Implement file integrity monitoring on trash/cleanup utilities and other maintenance-critical executables to detect unauthorized replacements or symlink redirection. On systems with process auditing enabled, search for suspicious child processes spawned by OpenClaw maintenance tasks with unexpected command lines or parent-child relationships that suggest path traversal manipulation.

Why prioritize this

This vulnerability should be prioritized for remediation because it enables local code execution with moderate effort by unprivileged users. While the attack vector is local and requires user access, the high impact on data confidentiality and integrity, combined with the low complexity of exploitation, makes it a practical escalation path in multi-user or compromised environments. Organizations with restrictive network segmentation but lax local access controls are especially at risk. The lack of KEV (Known Exploited Vulnerability) status does not diminish the threat; patching should not be deferred.

Risk score, explained

The CVSS 3.1 score of 7.1 (HIGH) appropriately reflects the risk profile. The local attack vector and low privilege requirement limit the immediate blast radius but indicate a meaningful insider or post-compromise risk. The high confidentiality and integrity impact scores reflect the ability to execute arbitrary code and access protected data. The absence of availability impact (the attack does not target denial of service) slightly reduces the score, but the overall HIGH rating is justified given the direct code execution capability and the low barrier to exploitation once local access is established.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. CVE-2026-53865 requires local access to the system running OpenClaw. It cannot be exploited over a network. The attacker must have already gained local access or unprivileged user account privileges on the target system.

What versions of OpenClaw are affected?

All versions before 2026.5.2 are affected. Verify your installed version and upgrade immediately if you are running an earlier release.

Do I need to restart OpenClaw after patching?

Yes. After upgrading to version 2026.5.2, restart the OpenClaw service to ensure the patched code is active. You should also monitor the first maintenance cycle after restart to confirm normal operation.

How can I detect if this vulnerability has been exploited in my environment?

Review maintenance task execution logs and process audit logs for unexpected command executions or environment variable anomalies tied to maintenance operations. Look for references to executables in unusual paths or symlinks created in workspace directories. File integrity monitoring on maintenance utilities will alert you to tampering.

This analysis is based on publicly available vulnerability data and the vendor's description. Organizations should verify the applicability of this vulnerability to their specific OpenClaw deployment and configuration. Patch testing should be conducted in a controlled environment before production deployment. For the most current and detailed guidance, refer to the official OpenClaw security advisory and vendor documentation. SEC.co makes no warranty regarding the completeness or accuracy of remediation guidance and recommends consultation with vendor support for environment-specific questions. Source: NVD (public-domain), retrieved 2026-07-24. Analysis generated by SEC.co (claude-haiku-4-5).