GHSA-H9XM-J4QG-FVPG

Vulnerability from github – Published: 2026-03-03 21:37 – Updated: 2026-03-30 13:46
VLAI
Summary
OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)
Details

Summary

In some opt-in sandbox configurations, the experimental apply_patch tool did not consistently apply workspace-only checks to mounted paths (for example /agent/...).

Impact

This does not affect default installs.

Default posture: - agents.defaults.sandbox.mode=off (sandbox disabled by default) - tools.exec.applyPatch.enabled=false (experimental tool disabled by default)

This behavior applies only when all of the following are enabled/configured: - sandbox mode, - experimental apply_patch, - workspace-only expectations (tools.fs.workspaceOnly=true and/or tools.exec.applyPatch.workspaceOnly=true), - and writable mounts outside workspace.

Under that opt-in setup, apply_patch operations could target mounted paths outside the workspace root.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected published versions: <= 2026.2.22-2
  • Fixed in code on main: commit 6634030be31e1a1842967df046c2f2e47490e6bf
  • Patched release: 2026.2.23

Technical Details

In the sandbox path flow, apply_patch used sandbox.bridge.resolvePath(...) without applying the same workspace-root assertion used by other filesystem tools. The fix makes apply_patch follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with tools.exec.applyPatch.workspaceOnly=false).

Fix Commit(s)

  • 6634030be31e1a1842967df046c2f2e47490e6bf

Release Process Note

patched_versions is pre-set to the released version (2026.2.23). Patched in 2026.2.23 and published.

OpenClaw thanks @tdjackey for reporting.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "openclaw"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2026.2.23"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32007"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22",
      "CWE-284",
      "CWE-863"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-03T21:37:11Z",
    "nvd_published_at": "2026-03-19T22:16:33Z",
    "severity": "HIGH"
  },
  "details": "### Summary\nIn some opt-in sandbox configurations, the **experimental** `apply_patch` tool did not consistently apply workspace-only checks to mounted paths (for example `/agent/...`).\n\n### Impact\nThis does **not** affect default installs.\n\nDefault posture:\n- `agents.defaults.sandbox.mode=off` (sandbox disabled by default)\n- `tools.exec.applyPatch.enabled=false` (experimental tool disabled by default)\n\nThis behavior applies only when all of the following are enabled/configured:\n- sandbox mode,\n- experimental `apply_patch`,\n- workspace-only expectations (`tools.fs.workspaceOnly=true` and/or `tools.exec.applyPatch.workspaceOnly=true`),\n- and writable mounts outside workspace.\n\nUnder that opt-in setup, `apply_patch` operations could target mounted paths outside the workspace root.\n\n### Affected Packages / Versions\n- Package: `openclaw` (npm)\n- Affected published versions: `\u003c= 2026.2.22-2`\n- Fixed in code on `main`: commit `6634030be31e1a1842967df046c2f2e47490e6bf`\n- Patched release: `2026.2.23`\n\n### Technical Details\nIn the sandbox path flow, `apply_patch` used `sandbox.bridge.resolvePath(...)` without applying the same workspace-root assertion used by other filesystem tools. The fix makes `apply_patch` follow the same workspace-only enforcement for sandbox-resolved paths (unless explicitly disabled with `tools.exec.applyPatch.workspaceOnly=false`).\n\n### Fix Commit(s)\n- `6634030be31e1a1842967df046c2f2e47490e6bf`\n\n### Release Process Note\n`patched_versions` is pre-set to the released version (`2026.2.23`). Patched in `2026.2.23` and published.\n\nOpenClaw thanks @tdjackey for reporting.",
  "id": "GHSA-h9xm-j4qg-fvpg",
  "modified": "2026-03-30T13:46:57Z",
  "published": "2026-03-03T21:37:11Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-h9xm-j4qg-fvpg"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32007"
    },
    {
      "type": "WEB",
      "url": "https://github.com/openclaw/openclaw/commit/6634030be31e1a1842967df046c2f2e47490e6bf"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/openclaw/openclaw"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/openclaw-sandbox-bypass-in-apply-patch-tool-via-workspace-only-check-bypass"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "OpenClaw: Experimental apply_patch may bypass workspace-only checks in opt-in sandbox mounts (off by default)"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…