# GHSA-796m-2973-wc5q: OpenClaw has exec allowlist/safeBins policy-runtime mismatch via env -S wrapper interpretation

> Attackers can bypass exec allowlists via env wrapper mismatches to execute arbitrary commands, requiring an upgrade to the patched version.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Mar 2026

## What is GHSA-796m-2973-wc5q?

GHSA-796m-2973-wc5q is a vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Summary
`tools.exec` allowlist/safe-bins evaluation could diverge from runtime execution for wrapper commands using GNU `env -S/--split-string` semantics. This allowed policy checks to treat a command as a benign safe-bin invocation while runtime executed a different payload.

### Affected Packages / Versions
- Package: `openclaw` (npm)
- Vulnerable versions: `<= 2026.2.22-2` (latest currently published npm version)
- Patched version (released): `2026.2.23`

### Impact
An attacker able to influence tool command text (for example via untrusted prompt/content injection reaching an exec-capable flow) could bypass allowlist/safe-bins intent and execute unexpected commands.

### Technical Details
Root cause was policy/runtime interpretation mismatch for dispatch wrappers:
- analysis resolved an effective executable from wrapper-unwrapped argv,
- execution could still run original wrapper argv semantics,
- safe-bin short-flag handling also allowed unknown short options in clusters.

### Remediation
The fix hardens exec approvals to fail closed and enforce analysis/runtime parity:
- introduce wrapper execution planning with semantic-wrapper blocking,
- carry planned `effectiveArgv` + `policyBlocked` metadata through resolution,
- evaluate allowlist/safe-bins against planned argv,
- enforce canonical rebuilt shell command from planned argv for allowlist auto-paths,
- use planned argv for node-host/mac exec-host invocation paths,
- reject unknown short safe-bin flags,
- add regression tests for semantic `env` wrappers and parity fixtures.

### Fix Commit(s)
- `a1c4bf07c6baad3ef87a0e710fe9aef127b1f606`

### Release Process Note
`patched_versions` is pre-set to the released version (`2026.2.23`). Patched in `2026.2.23` and published.

OpenClaw thanks @jiseoung for reporting.

## Which versions are affected by GHSA-796m-2973-wc5q?

2 open source packages ship an affected version, including openclaw.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.23 |
| `openclaw` | npm | All versions | 2026.2.23 |

## How do I fix GHSA-796m-2973-wc5q?

Upgrade openclaw to 2026.2.23 or later.

## Is GHSA-796m-2973-wc5q being exploited?

There is no known exploitation of GHSA-796m-2973-wc5q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-796m-2973-wc5q and fix it if it is affected.

What it is: GHSA-796m-2973-wc5q is a vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-796m-2973-wc5q in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.23
- openclaw (npm): affected all versions; fixed in 2026.2.23

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-796m-2973-wc5q/ (Markdown: https://insights.sbomify.com/GHSA-796m-2973-wc5q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-796m-2973-wc5q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-796m-2973-wc5q/
Summaries are generated and may contain mistakes; the official description above is the record.