# GHSA-3h2q-j2v4-6w5r: OpenClaw's system.run allowlist approval parsing missed PowerShell encoded-command wrappers

> Attackers with system.run access can bypass allowlist approval to execute PowerShell payloads via encoded commands in OpenClaw.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2026

## What is GHSA-3h2q-j2v4-6w5r?

GHSA-3h2q-j2v4-6w5r is a vulnerability in openclaw, published on 9 Mar 2026. 

### Official description

OpenClaw's `system.run` shell-wrapper detection did not recognize PowerShell `-EncodedCommand` forms as inline-command wrappers.

In `allowlist` mode, a caller with access to `system.run` could invoke `pwsh` or `powershell` using `-EncodedCommand`, `-enc`, or `-e`, and the request would fall back to plain argv analysis instead of the normal shell-wrapper approval path. This could allow a PowerShell inline payload to execute without the approval step that equivalent `-Command` invocations would require.

Latest published npm version: `2026.3.2`

Fixed on `main` on March 7, 2026 in `1d1757b16f48f1a93cd16ab0ad7e2c3c63ce727d` by recognizing PowerShell encoded-command aliases during shell-wrapper parsing, so allowlist mode continues to require approval for those payloads. Normal approved PowerShell wrapper flows continue to work.

## Affected Packages / Versions

- Package: `openclaw` (npm)
- Affected versions: `<= 2026.3.2`
- Patched version: `>= 2026.3.7`

## Fix Commit(s)

- `1d1757b16f48f1a93cd16ab0ad7e2c3c63ce727d`

## Release Process Note

npm `2026.3.7` was published on March 8, 2026. This advisory is fixed in the released package.

Thanks @tdjackey for reporting.

## Which versions are affected by GHSA-3h2q-j2v4-6w5r?

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


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

## How do I fix GHSA-3h2q-j2v4-6w5r?

Upgrade openclaw to 2026.3.7 or later.

## Is GHSA-3h2q-j2v4-6w5r being exploited?

There is no known exploitation of GHSA-3h2q-j2v4-6w5r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3h2q-j2v4-6w5r and fix it if it is affected.

What it is: GHSA-3h2q-j2v4-6w5r is a vulnerability in openclaw, published on 9 Mar 2026. 
Exploitation: There is no known exploitation of GHSA-3h2q-j2v4-6w5r in the wild and no public exploit code.

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

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-3h2q-j2v4-6w5r/ (Markdown: https://insights.sbomify.com/GHSA-3h2q-j2v4-6w5r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3h2q-j2v4-6w5r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3h2q-j2v4-6w5r/
Summaries are generated and may contain mistakes; the official description above is the record.