GHSA-XMV6-R34M-62P4

GHSA-XMV6-R34M-62P4 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions <= 2026.2.24. It is fixed in 2026.2.25.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

OpenClaw: Sandbox media fallback tmp symlink alias bypass allows host file reads outside sandboxRoot

A sandbox path validation bypass in openclaw allows host file reads outside sandboxRoot via the media path fallback tmp flow when the fallback tmp root is a symlink alias.

Affected Packages / Versions

  • Package: npm openclaw
  • Affected versions: <= 2026.2.24
  • Latest published npm version at triage time (February 26, 2026): 2026.2.24
  • Patched version : 2026.2.25

Details

When /tmp/openclaw is unavailable or unsafe, resolvePreferredOpenClawTmpDir() in src/infra/tmp-openclaw-dir.ts fell back to os.tmpdir()/openclaw-<uid> without verifying that fallback path was a trusted non-symlink directory.

resolveSandboxedMediaSource() (src/agents/sandbox-paths.ts) allows absolute tmp media paths under the OpenClaw tmp root using lexical containment and alias checks. If the fallback tmp root is a symlink alias (for example to /), inputs like $TMPDIR/openclaw-<uid>/etc/passwd can pass validation and resolve to host files outside sandboxRoot.

Reproduction (high level)

  1. Force resolver fallback (make /tmp/openclaw unavailable/invalid).
  2. Make fallback root ($TMPDIR/openclaw-<uid>) a symlink alias to /.
  3. Submit media path under fallback root (for example $TMPDIR/openclaw-<uid>/etc/passwd).
  4. Observe accepted path and read outside sandboxRoot.

Fix Commit(s)

  • 496a76c03ba85e15ea715e5a583e498ae04d36e3

Release Process Note

Patched version is pre-set to release 2026.2.25; once npm publish for 2026.2.25 is complete, this advisory can be published without further metadata edits.

OpenClaw thanks @tdjackey for reporting.

Impact

This can break sandbox media path confinement and permit unauthorized host file reads (confidentiality impact).

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.

Affected versions

openclaw (<= 2026.2.24)

Security releases

openclaw → 2026.2.25 (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.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade openclaw to 2026.2.25 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-XMV6-R34M-62P4? GHSA-XMV6-R34M-62P4 is a high-severity path traversal vulnerability in openclaw (npm), affecting versions <= 2026.2.24. It is fixed in 2026.2.25. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
  2. Which versions of openclaw are affected by GHSA-XMV6-R34M-62P4? openclaw (npm) versions <= 2026.2.24 is affected.
  3. Is there a fix for GHSA-XMV6-R34M-62P4? Yes. GHSA-XMV6-R34M-62P4 is fixed in 2026.2.25. Upgrade to this version or later.
  4. Is GHSA-XMV6-R34M-62P4 exploitable, and should I be worried? Whether GHSA-XMV6-R34M-62P4 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
  5. What actually determines whether GHSA-XMV6-R34M-62P4 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.
  6. How do I fix GHSA-XMV6-R34M-62P4? Upgrade openclaw to 2026.2.25 or later.

Other vulnerabilities in openclaw

Stop the waste.
Protect your environment with Kodem.