CVE-2026-53865
Description
OpenClaw before 2026.5.2 allows path traversal in maintenance tasks, letting attackers execute unintended local executables via workspace-derived service paths.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
OpenClaw before 2026.5.2 allows path traversal in maintenance tasks, letting attackers execute unintended local executables via workspace-derived service paths.
Vulnerability
OpenClaw before version 2026.5.2 contains a path traversal vulnerability in maintenance task execution. The workspace-derived environment path can influence trash command selection, allowing an attacker to run unintended local executables from operator-unintended paths during maintenance operations. [1][2]
Exploitation
An attacker with local authenticated access as an operator can manipulate workspace-derived environment paths to cause maintenance tasks to select and execute a malicious trash executable from an unintended location. This requires the affected feature to be enabled and the operator to have the ability to influence workspace configurations. [1]
Impact
Successful exploitation allows the attacker to execute arbitrary local executables from a path the operator did not intend. The practical impact depends on the operator's configuration and whether lower-trust input can reach that path. According to the advisory, it does not change OpenClaw's trusted-operator model. [1]
Mitigation
The first stable patched version is 2026.5.2. As a workaround, keep maintenance flows on trusted workspaces and fixed service paths until patched. Also keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when not needed. [1]
AI Insight generated on Jun 16, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.