OpenClaw 2.0.0-beta3 < 2026.2.14 - Arbiträres Laden von JavaScript-Modulen über Hook Transform Path Traversal

The path traversal vulnerability in OpenClaw's hook transform module loading process is particularly concerning due to its potential for remote code execution. An attacker who can modify the hooks.mappings[].transform.module parameter can supply absolute paths or traversal sequences to load and execute malicious JavaScript modules. Given that the gateway process typically runs with elevated privileges, successful exploitation could grant the attacker significant control over the system. This could involve data theft, system disruption, or even complete takeover of the OpenClaw instance. The ability to execute arbitrary JavaScript within the context of the gateway process significantly expands the attack surface.

Organizations and individuals using OpenClaw, particularly those with publicly accessible instances or those who allow external users to modify configuration files, are at risk. Environments where OpenClaw is integrated with other systems or services are also at increased risk due to the potential for lateral movement.

• javascript: Examine OpenClaw configuration files for suspicious entries in the hooks.mappings[].transform.module parameter, particularly those containing absolute paths or traversal sequences (e.g., ../). • javascript: Monitor OpenClaw logs for errors or warnings related to module loading failures, which could indicate an attempted exploitation. • javascript: Use a debugger to step through the hook transform module loading process and identify any unexpected file access patterns.

1. 2026-03-05Disclosure

   disclosure

1. Reserviert2026-02-27
2. Veröffentlicht2026-03-05
3. Geändert2026-03-11
4. EPSS aktualisiert2026-03-23

The primary mitigation for CVE-2026-28393 is to immediately upgrade OpenClaw to version 2026.2.14 or later. Prior to upgrading, it's crucial to back up your OpenClaw configuration files to facilitate a rollback if the upgrade introduces unforeseen compatibility issues. If upgrading is not immediately feasible, restrict write access to the configuration files to only authorized personnel. Implement strict input validation on any user-supplied data used to configure the hook transform module. While a WAF or proxy cannot directly prevent this vulnerability, it can help detect and block suspicious requests attempting to exploit it by monitoring for unusual file paths or JavaScript execution patterns. After upgrading, confirm the fix by attempting to load a malicious module via the hooks.mappings[].transform.module parameter and verifying that the attempt is denied.