CVE-2026-28456

OpenClaw Gateway supports hook mappings with optional JavaScript/TypeScript transform modules. In affected versions, the gateway did not sufficiently constrain configured module paths before passing them to dynamic import(). Under some configurations, a user who can modify gateway configuration could cause the gateway process to load and execute an unintended local module.

Affected Packages / Versions

• npm package: openclaw
• Affected: >= 2026.1.5 and <= 2026.2.13

Patched Versions

• >= 2026.2.14

Fix Commit(s)

• a0361b8ba959e8506dc79d638b6e6a00d12887e4 (restrict hook transform module loading)
• 35c0e66ed057f1a9f7ad2515fdcef516bd6584ce (harden hooks module loading)

Mitigation

• Upgrade to 2026.2.14 or newer.
• Avoid exposing gateway configuration endpoints to untrusted networks.
• Review config for unsafe values:
  • hooks.mappings[].transform.module
  • hooks.internal.handlers[].module

Thanks @222n5 for reporting.

Potential code execution in the OpenClaw gateway Node.js process.

This requires access that can modify gateway configuration (for example via the gateway config endpoints). Treat such access as high privilege.

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-28456 has a CVSS score of 7.2 (High). The vector is network-reachable, 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.

Kodem intelligence

1. What is CVE-2026-28456? CVE-2026-28456 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions >= 2026.1.5, < 2026.2.14. 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-28456? CVE-2026-28456 has a CVSS score of 7.2 (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-28456? openclaw (npm) versions >= 2026.1.5, < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-28456? Yes. CVE-2026-28456 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-28456 exploitable, and should I be worried? Whether CVE-2026-28456 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-28456 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-28456? Upgrade openclaw to 2026.2.14 or later.