# GHSA-8m9v-xpgf-g99m: OpenClaw has an unauthorized sender bypass in its stop triggers and /models command authorization

> Unauthorized senders can bypass authorization checks to disrupt sessions and view sensitive model metadata in OpenClaw.

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

## What is GHSA-8m9v-xpgf-g99m?

GHSA-8m9v-xpgf-g99m is a missing authorization vulnerability in openclaw, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary
Unauthorized senders could trigger two command paths without sender authorization checks:
1. stop-like natural-language abort triggers
2. `/models` command output

### Impact
An unauthorized sender could disrupt active sessions and view model/auth metadata that should be authorization-gated.

### Fix
Sender authorization is now enforced for stop-like abort triggers and `/models` listings.

### Affected and Patched Versions
- Affected: `<= 2026.2.26`
- Patched: `2026.3.1`

## Which versions are affected by GHSA-8m9v-xpgf-g99m?

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


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

## How do I fix GHSA-8m9v-xpgf-g99m?

Upgrade openclaw to 2026.3.1 or later.

## Is GHSA-8m9v-xpgf-g99m being exploited?

There is no known exploitation of GHSA-8m9v-xpgf-g99m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-8m9v-xpgf-g99m and fix it if it is affected.

What it is: GHSA-8m9v-xpgf-g99m is a missing authorization vulnerability in openclaw, published on 2 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8m9v-xpgf-g99m in the wild and no public exploit code.

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

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-8m9v-xpgf-g99m/ (Markdown: https://insights.sbomify.com/GHSA-8m9v-xpgf-g99m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-8m9v-xpgf-g99m

---
From sbomify Insights: https://insights.sbomify.com/GHSA-8m9v-xpgf-g99m/
Summaries are generated and may contain mistakes; the official description above is the record.