CVE-2026-28393

CVE-2026-28393 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions >= 2.0.0-beta3, <= 2026.2.13. It is fixed in 2026.2.14.

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.

Reproduction (config-controlled module load)

  1. Configure a hook mapping that points to a transform path that escapes the transforms directory (for example via .. traversal).
  2. Place a malicious ESM module at the resolved location that executes arbitrary code in the gateway process.
  3. Trigger the hook endpoint with the correct hook token.

Credits

OpenClaw thanks @akhmittra for reporting.

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.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

CVE-2026-28393 has a CVSS score of 6.0 (High). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.14); upgrading removes the vulnerable code path.

Affected versions

openclaw (>= 2.0.0-beta3, <= 2026.2.13)

Security releases

openclaw → 2026.2.14 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Transform loading is now constrained to the OpenClaw transforms root directory:

  • Root: ~/.openclaw/hooks/transforms
  • hooks.transformsDir must be within that directory
  • transform.module must be within the selected transforms directory

Attempts to escape the root (absolute paths outside, .. traversal) are rejected.

Fix commit(s):

  • a0361b8ba959e8506dc79d638b6e6a00d12887e4
  • 18e8bd68c5015a894f999c6d5e6e32468965bfb5

Frequently Asked Questions

  1. What is CVE-2026-28393? CVE-2026-28393 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions >= 2.0.0-beta3, <= 2026.2.13. It is fixed in 2026.2.14. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. How severe is CVE-2026-28393? CVE-2026-28393 has a CVSS score of 6.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of openclaw are affected by CVE-2026-28393? openclaw (npm) versions >= 2.0.0-beta3, <= 2026.2.13 is affected.
  4. Is there a fix for CVE-2026-28393? Yes. CVE-2026-28393 is fixed in 2026.2.14. Upgrade to this version or later.
  5. Is CVE-2026-28393 exploitable, and should I be worried? Whether CVE-2026-28393 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-28393 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-28393? Upgrade openclaw to 2026.2.14 or later.

Other vulnerabilities in openclaw

CVE-2026-53811CVE-2026-53816CVE-2026-53806CVE-2026-53818CVE-2026-53809

Stop the waste.
Protect your environment with Kodem.