CVE-2026-28462

OpenClaw’s browser control API accepted user-supplied output paths for trace/download files without consistently
constraining writes to OpenClaw-managed temporary directories.

Impact

If an attacker can access the browser control API, they could attempt to write trace/download output files outside
intended temp roots, depending on process filesystem permissions.

Affected versions

openclaw < 2026.2.13

Fixed versions

openclaw >= 2026.2.13

Remediation

Upgrade to 2026.2.13 or later.

What changed

The fix constrains output paths for:

• POST /trace/stop
• POST /wait/download
• POST /download

All three now enforce OpenClaw temp-root boundaries and reject traversal/escape paths.

Credits

Thanks to Adnan Jakati (@jackhax) of Praetorian for responsible disclosure.

Fix shipped in PR #15652 and merged to main on February 13, 2026 (7f0489e4731c8d965d78d6eac4a60312e46a9426).

Fix commit 7f0489e4731c8d965d78d6eac4a60312e46a9426 confirmed on main and in v2026.2.14. Upgrade to openclaw >= 2026.2.13.

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-28462 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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.13); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-28462? CVE-2026-28462 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.13. It is fixed in 2026.2.13. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. How severe is CVE-2026-28462? CVE-2026-28462 has a CVSS score of 7.5 (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-28462? openclaw (npm) versions < 2026.2.13 is affected.
4. Is there a fix for CVE-2026-28462? Yes. CVE-2026-28462 is fixed in 2026.2.13. Upgrade to this version or later.
5. Is CVE-2026-28462 exploitable, and should I be worried? Whether CVE-2026-28462 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-28462 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-28462? Upgrade openclaw to 2026.2.13 or later.