High

OpenClaw's POSIX node system.run safe-bin allowlist could be widened by shell expansion

  • Disclosed: 02.07.2026
  • Updated: 11.10.2026 10:22

Summary

On POSIX nodes, OpenClaw's system.run safe-bin checks could approve a command before shell expansion changed how the command was interpreted. A value that appeared to be a safe-bin argument could expand into additional shell words and become a file operand.

This issue is limited to paired POSIX node execution through system.run with safe-bin or allowlist-style auto-approval. It is not an unauthenticated node takeover.

Affected configurations

This affects deployments where:

  • a POSIX node is paired to the gateway
  • system.run is reachable by an authenticated operator or agent flow
  • exec policy uses safe-bin or allowlist-based auto-approval
  • the approved command contains shell-expanded values that can change argv shape

Impact

A lower-privilege operator flow could cause an approved safe-bin command to read a node-local file that was not intended by the policy. Depending on the local files available to the node process, this could expose OpenClaw configuration data or other node-local information.

The issue is a policy-enforcement gap in argv validation, not a general statement that every safe-bin command is unsafe.

Patched Versions

The first stable patched version is 2026.5.18.

Mitigations

Upgrade to openclaw@2026.5.18 or later. Before upgrading, avoid broad safe-bin auto-approval for commands that can read arbitrary paths, and prefer explicit approval for node commands that touch local files.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package openclaw < 2026.5.18 2026.5.18

References

CVSS score 7.1/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
Weakness (CWE)
CWE-200, CWE-284, CWE-367, CWE-78
Platform
npm
Package
openclaw
Disclosed
02.07.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-mhq8-78pj-5j79 - CC BY 4.0

Vulnerability history: openclaw

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (588) in the archive
Total entries
588
First → latest
02.2026 07.2026
Without a fix
9
Exploited in attacks
0

Severity breakdown

  • Critical 20
  • High 215
  • Medium 299
  • Low 54

Disclosures per year

  1. 2026: 588
Severity:
  1. High · 8.8 CVE-2026-53811 < 2026.5.7 2026.5.7
  2. High · 8.8 CVE-2026-53806 < 2026.5.12 2026.5.12
  3. High · 7.8 CVE-2026-53813 < 2026.4.25 2026.4.25
  4. High · 7.5 CVE-2026-53834 < 2026.4.27 2026.4.27
  5. Critical CVE-2026-34507 < 2026.4.29 2026.4.29
  6. High CVE-2026-53823 < 2026.5.3 2026.5.3
  7. OpenClaw's POSIX node system.run safe-bin allowlist could be widened by shell expansion this entry
    High · 7.1 CVE-2026-53831 < 2026.5.18 2026.5.18
  8. High · 8.4 CVE-2026-53814 < 2026.5.20 2026.5.20
Show more (20) Showing 20 of 235

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.