# GHSA-hfpr-jhpq-x4rm: OpenClaw: `operator.write` chat.send could reach admin-only config writes

> Authenticated operator.write users can escalate privileges to modify admin-only configuration via chat.send, requiring an upgrade to fix.

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

## What is GHSA-hfpr-jhpq-x4rm?

GHSA-hfpr-jhpq-x4rm is a vulnerability in openclaw, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Summary
A gateway client authenticated with `operator.write` could route `/config set` or `/config unset` through `chat.send` and reach persistent config mutation even though direct config RPC methods are admin-scoped.

### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published vulnerable version: `2026.3.2`
- Affected range: `<= 2026.3.2`
- Patched in: `2026.3.7`

### Details
Before the fix, `chat.send` ran slash commands in an internal gateway-chat context with `CommandAuthorized: true`, and `/config` write paths only checked command authorization plus `commands.config` / `channels.<provider>.configWrites` gates. That allowed an authenticated `operator.write` gateway client to bridge into persistent config writes even though direct `config.*` RPC methods remain `operator.admin` scoped.

The fix keeps command functionality intact while restoring the intended scope boundary:
- persistent `/config set|unset` writes routed through gateway `chat.send` now require `operator.admin`
- read-only `/config show` remains available to normal write-scoped gateway clients
- normal messaging-channel `/config` behavior remains unchanged

### Impact
This is a real authorization mismatch, but exploitability requires an already authenticated gateway client with `operator.write`, `chat.send` access, and `/config` command support enabled. Maintainer severity is set to medium because the bug is a scoped control-plane privilege mismatch rather than a broad unauthenticated or generic remote compromise. The main consequence is unintended persistent config mutation.

### Fix Commit(s)
- `5f8f58ae25e2a78f31b06edcf26532d634ca554e`

### 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-hfpr-jhpq-x4rm?

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-hfpr-jhpq-x4rm?

Upgrade openclaw to 2026.3.7 or later.

## Is GHSA-hfpr-jhpq-x4rm being exploited?

There is no known exploitation of GHSA-hfpr-jhpq-x4rm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hfpr-jhpq-x4rm and fix it if it is affected.

What it is: GHSA-hfpr-jhpq-x4rm is a vulnerability in openclaw, published on 9 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-hfpr-jhpq-x4rm 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-hfpr-jhpq-x4rm/ (Markdown: https://insights.sbomify.com/GHSA-hfpr-jhpq-x4rm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hfpr-jhpq-x4rm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hfpr-jhpq-x4rm/
Summaries are generated and may contain mistakes; the official description above is the record.