CVE-2026-32060: Openclaw Path Traversal Vulnerability

HIGH
Advisory Identifier: GHSA-r5fq-947m-xm57
CVSS 8.8
CWE-22
Published
Advisory Summary

CVE-2026-32060 is a HIGH (CVSS 8.8) path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Openclaw libraries in the npm ecosystem. The issue involves openclaw has a path traversal in apply_patch could write/delete files outside the workspace. Remediation is available by upgrading affected packages to version 2026.2.14.

CVE-2026-32060 at a Glance

CVE Identifier CVE-2026-32060
GHSA Identifier GHSA-r5fq-947m-xm57
Severity HIGH
CVSS v3.1 Base Score 8.8
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Openclaw
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 8.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-32060

To remediate this vulnerability, upgrade all affected Openclaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.2.14
npm install openclaw@2026.2.14
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-32060, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of Openclaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.2.14), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Openclaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary In affected versions, when `apply_patch` was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected: `<= 2026.2.13` - Fixed: `>= 2026.2.14` ## Details The non-sandbox path resolution in `apply_patch` did not enforce workspace containment. Inputs like `../../...` or absolute paths could escape the working directory in non-sandboxed mode. ## Impact Practical impact depends on deployment and who can trigger tool execution. This is most relevant when tool invocation is exposed to less-trusted callers or when operators expected workspace-only containment. ## Workarounds - Keep `tools.exec.applyPatch.enabled` disabled if you do not need `apply_patch`. - Keep `tools.exec.applyPatch.workspaceOnly` at its secure default of `true`. - Restrict who can trigger tool execution (and which tools are allowlisted). ## Configuration Note `tools.exec.applyPatch.workspaceOnly: false` intentionally opts out of workspace containment and can re-enable outside-workspace writes/deletes. ## Fix - PR: https://github.com/openclaw/openclaw/pull/16405 - Merge commit: `5544646a09c0121fca7d7093812dc2de8437c7f1` ## Credits Thanks to @p80n-sec for reporting this issue.

CVE-2026-32060 Affected Openclaw Versions

1 component(s)
Fixed Versions:
2026.2.14
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm
< 2026.2.14
2026.2.14

References

Frequently Asked Questions

What is CVE-2026-32060?
CVE-2026-32060 is a security vulnerability in Openclaw involving OpenClaw has a path traversal in apply_patch could write/delete files outside the workspace under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Openclaw versions are affected?
Affected versions include releases prior to 2026.2.14 across affected packages: openclaw.
What version fixes CVE-2026-32060?
Upgrading to 2026.2.14 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.2.14. Upgrade your dependency to 2026.2.14 or later.
What is the CVSS score of CVE-2026-32060?
CVE-2026-32060 has a CVSS v3.1 base score of 8.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-32060?
CVE-2026-32060 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check npm dependencies for CVE-2026-32060?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r5fq-947m-xm57",
  "modified" : "2026-03-11T20:38:25Z",
  "published" : "2026-02-19T20:45:58Z",
  "aliases" : [ "CVE-2026-32060" ],
  "summary" : "OpenClaw has a path traversal in apply_patch could write/delete files outside the workspace",
  "details" : "## Summary\n\nIn affected versions, when `apply_patch` was enabled and the agent ran without filesystem sandbox containment, crafted paths could cause file writes/deletes outside the configured workspace directory.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Affected: `<= 2026.2.13`\n- Fixed: `>= 2026.2.14`\n\n## Details\n\nThe non-sandbox path resolution in `apply_patch` did not enforce workspace containment. Inputs like `../../...` or absolute paths could escape the working directory in non-sandboxed mode.\n\n## Impact\n\nPractical impact depends on deployment and who can trigger tool execution. This is most relevant when tool invocation is exposed to less-trusted callers or when operators expected workspace-only containment.\n\n## Workarounds\n\n- Keep `tools.exec.applyPatch.enabled` disabled if you do not need `apply_patch`.\n- Keep `tools.exec.applyPatch.workspaceOnly` at its secure default of `true`.\n- Restrict who can trigger tool execution (and which tools are allowlisted).\n\n## Configuration Note\n\n`tools.exec.applyPatch.workspaceOnly: false` intentionally opts out of workspace containment and can re-enable outside-workspace writes/deletes.\n\n## Fix\n\n- PR: https://github.com/openclaw/openclaw/pull/16405\n- Merge commit: `5544646a09c0121fca7d7093812dc2de8437c7f1`\n\n## Credits\n\nThanks to @p80n-sec for reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.2.14"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-r5fq-947m-xm57"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32060"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/pull/16405"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/5544646a09c0121fca7d7093812dc2de8437c7f1"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/releases/tag/v2026.2.14"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/openclaw-path-traversal-in-apply-patch-via-crafted-paths"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-19T20:45:58Z",
    "nvd_published_at" : "2026-03-11T14:16:27Z"
  }
}