# GHSA-f6h3-846h-2r8w: OpenClaw's elevated allowFrom accepted broader identity signals than specified within sender-scoped authorization

> Attackers can bypass elevated sender authorization checks in OpenClaw by exploiting broader identity signal matching in specific configurations.

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

## What is GHSA-f6h3-846h-2r8w?

GHSA-f6h3-846h-2r8w is a missing authorization vulnerability in openclaw, published on 4 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Summary
In certain elevated-mode configurations, `tools.elevated.allowFrom` accepted broader identity signals than intended. The fix tightens matching to sender-scoped identity by default and makes mutable metadata matching explicit.

### Context
OpenClaw is commonly used in 1:1 chats or trusted group chats. In that intended model, this issue is best treated as authorization hardening / defense-in-depth for elevated sender approval.

### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published npm version at triage: `2026.2.21-2`
- Affected versions: `<= 2026.2.21-2`
- Planned patched version (pre-set for publish-ready advisory): `2026.2.22`

### Details
Elevated sender authorization now matches sender-scoped identity values only by default (`SenderId`, `From`, `SenderE164`) and no longer considers recipient routing fields such as `ctx.To`.

Mutable sender metadata (`SenderName`, `SenderUsername`, `SenderTag`) now requires explicit allowlist prefixes (`name:`, `username:`, `tag:`). Explicit identity prefixes are also supported (`id:`, `from:`, `e164:`).

### Fix Commit(s)
- `6817c0ec7b4fa830123d4f5c340f075a4bd04ee2`

### Release Process Note
The advisory `patched_versions` is pre-set to the planned next release (`2026.2.22`). Once npm `openclaw@2026.2.22` is published, this advisory can be published without additional content edits.

OpenClaw thanks @jiseoung for reporting.

## Which versions are affected by GHSA-f6h3-846h-2r8w?

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


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

## How do I fix GHSA-f6h3-846h-2r8w?

Upgrade openclaw to 2026.2.22 or later.

## Is GHSA-f6h3-846h-2r8w being exploited?

There is no known exploitation of GHSA-f6h3-846h-2r8w in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f6h3-846h-2r8w and fix it if it is affected.

What it is: GHSA-f6h3-846h-2r8w is a missing authorization vulnerability in openclaw, published on 4 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-f6h3-846h-2r8w in the wild and no public exploit code.

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

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-f6h3-846h-2r8w/ (Markdown: https://insights.sbomify.com/GHSA-f6h3-846h-2r8w/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f6h3-846h-2r8w

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f6h3-846h-2r8w/
Summaries are generated and may contain mistakes; the official description above is the record.