OpenClaw's hook transform module path allows traversal and arbitrary JavaScript module loading
Summary
OpenClaw hook mapping transforms could be loaded via absolute paths or .. traversal, allowing arbitrary JavaScript module loading/execution in the gateway process when an attacker can modify hooks configuration.
Affected Versions
- Affected: >= 2.0.0-beta3 and <= 2026.2.13
- Fixed: 2026.2.14
Details
hooks.mappings[].transform.module is dynamically imported and executed during webhook processing. Path resolution previously accepted absolute paths and did not enforce containment for relative paths, so a config-controlled transform could resolve outside the intended transforms directory.
Impact
If an attacker can write the OpenClaw config (or otherwise update hooks config through authenticated configuration mechanisms), they could point a hook mapping transform at an arbitrary module on disk and execute code with the gateway process privileges.
Reproduction (config-controlled module load)
- Configure a hook mapping that points to a transform path that escapes the transforms directory (for example via
..traversal). - Place a malicious ESM module at the resolved location that executes arbitrary code in the gateway process.
- Trigger the hook endpoint with the correct hook token.
Fix
Transform loading is now constrained to the OpenClaw transforms root directory:
- Root:
~/.openclaw/hooks/transforms hooks.transformsDirmust be within that directorytransform.modulemust be within the selected transforms directory
Attempts to escape the root (absolute paths outside, .. traversal) are rejected.
Fix commit(s):
- a0361b8ba959e8506dc79d638b6e6a00d12887e4
- 18e8bd68c5015a894f999c6d5e6e32468965bfb5
Credits
OpenClaw thanks @akhmittra for reporting.
| Software | From | Fixed in |
|---|---|---|
openclaw
|
2.0.0-beta3 | 2026.2.14 |
Deep Security Visibility Without the Complexity
SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.
- No setup fees
- 5-min deployment
- Cancel anytime
Frequently Asked Questions
A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.
CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.
A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.
Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.
Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.
SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.