Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-h9xm-j4qg-fvpg

MediumCVSS 6.8 / 10
Published Mar 3, 2026·Last modified Mar 30, 2026
Affected Components(0)

No affected components available

Description

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.

Risk Scores
Base Score
6.8

The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data.

Threat Intelligence
6.2

Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.

EPSS
0.36%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Medium severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard