# GHSA-2ch6-x3g4-7759: OpenClaw's commands.allowFrom sender authorization accepted conversation identifiers via ctx.From

> OpenClaw's command authorization incorrectly allowed conversation identifiers, enabling unauthorized users in a chat to execute privileged commands.

- **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:** 3 Mar 2026

## What is GHSA-2ch6-x3g4-7759?

GHSA-2ch6-x3g4-7759 is a missing authorization vulnerability in openclaw, published on 3 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Summary
`commands.allowFrom` is documented as a sender authorization allowlist for commands/directives, but command authorization could include `ctx.From` (conversation identity) as a sender candidate.

When `commands.allowFrom` contained conversation-like identifiers (for example Discord `channel:<id>` or WhatsApp group JIDs), command/directive authorization could be granted to participants in that conversation instead of only the intended sender identity.

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

### Details
Root cause: `resolveSenderCandidates()` in `src/auto-reply/command-auth.ts` always included `ctx.From` in candidate evaluation used by `commands.allowFrom` authorization checks.

`ctx.From` is sender-like in some direct-message contexts, but conversation-like in channel/group/thread contexts. This mixed principal handling allowed conversation identifiers to satisfy sender-only authorization.

### Impact
In affected versions, command/directive authorization could become broader than intended when operators configured `commands.allowFrom` with conversation identifiers, allowing unintended users in that conversation to run command-only/directive-only flows.

### Fix
Main branch now treats `commands.allowFrom` as sender-only:
- `ctx.From` is no longer included as a general sender candidate.
- `ctx.From` is only used as fallback when sender fields are absent and the value is not conversation-shaped.
- Regression tests were added for conversation-id denial and direct-message fallback preservation.

### Fix Commit(s)
- `08e2aa44e78a9c946d97bea62304e6f533b8fa8e`

### Release Process Note
`patched_versions` is pre-set to the released version (`2026.2.23`). This advisory now reflects released fix version `2026.2.23`.

OpenClaw thanks @jiseoung for reporting.

## Which versions are affected by GHSA-2ch6-x3g4-7759?

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-2ch6-x3g4-7759?

Upgrade openclaw to 2026.2.23 or later.

## Is GHSA-2ch6-x3g4-7759 being exploited?

There is no known exploitation of GHSA-2ch6-x3g4-7759 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2ch6-x3g4-7759 and fix it if it is affected.

What it is: GHSA-2ch6-x3g4-7759 is a missing authorization vulnerability in openclaw, published on 3 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-2ch6-x3g4-7759 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-2ch6-x3g4-7759/ (Markdown: https://insights.sbomify.com/GHSA-2ch6-x3g4-7759/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2ch6-x3g4-7759

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2ch6-x3g4-7759/
Summaries are generated and may contain mistakes; the official description above is the record.