CVE-2026-26972

OpenClaw browser download helpers accepted an unsanitized output path. When invoked via the browser control gateway routes, this allowed path traversal to write downloads outside the intended OpenClaw temp downloads directory.

This issue is not exposed via the AI agent tool schema (no download action). Exploitation requires authenticated CLI access or an authenticated gateway RPC token.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected: >=2026.1.12, <=2026.2.12
• Fixed: >=2026.2.13

Details

Affected code: src/browser/pw-tools-core.downloads.ts (waitForDownloadViaPlaywright, downloadViaPlaywright).

Fixed entrypoints (as of 2026.2.13):

• Gateway browser control routes /wait/download and /download now restrict path to DEFAULT_DOWNLOAD_DIR via resolvePathWithinRoot.

Fix Commit(s)

• 7f0489e4731c8d965d78d6eac4a60312e46a9426

Mitigation

Upgrade to openclaw >=2026.2.13.

Thanks @locus-x64 for reporting.

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-26972 has a CVSS score of 6.7 (Medium). 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.13); upgrading removes the vulnerable code path.

Kodem intelligence

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