# GHSA-4cqv-h74h-93j4: OpenClaw has a Discord `allowFrom` slug-collision authorization bypass

> OpenClaw allows unauthorized access via Discord name/tag slug collisions, bypassing allowlists configured with names instead of user IDs.

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

## What is GHSA-4cqv-h74h-93j4?

GHSA-4cqv-h74h-93j4 is an authentication bypass vulnerability in openclaw, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw supports Discord allowlists using either user IDs or names/tags. Name/tag matching depends on slug normalization, so different user tags can collide to the same slug and unintentionally satisfy a name-based allowlist entry.

## Affected Packages / Versions
- Package: `openclaw` (npm)
- Affected versions: `<= 2026.2.21-2`
- Patched versions: >= 2026.2.22

## What Changed
- `openclaw security audit` now warns on Discord name/tag allowlist entries (DM allowlists, guild/channel `users`, and pairing-store entries).
- Runtime authorization now prefers resolved user IDs when a configured name/tag can be resolved, without rewriting config files on disk.
- Name-based entries remain supported for compatibility.

## Recommendations
- Prefer stable Discord user IDs for security-sensitive allowlists.
- Run `openclaw security audit` and address warnings where practical.

## Fix Commit(s)
- f97c45c5b5e0698b6667bb5f6badc0cac7dabd12
- 747bb581b3f2264495e1fec5a0727d9f2ca1b6f1

OpenClaw thanks @tdjackey for reporting.

## Which versions are affected by GHSA-4cqv-h74h-93j4?

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-4cqv-h74h-93j4?

Upgrade openclaw to 2026.2.22 or later.

## Is GHSA-4cqv-h74h-93j4 being exploited?

There is no known exploitation of GHSA-4cqv-h74h-93j4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4cqv-h74h-93j4 and fix it if it is affected.

What it is: GHSA-4cqv-h74h-93j4 is an authentication bypass vulnerability in openclaw, published on 3 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-4cqv-h74h-93j4 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-4cqv-h74h-93j4/ (Markdown: https://insights.sbomify.com/GHSA-4cqv-h74h-93j4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4cqv-h74h-93j4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4cqv-h74h-93j4/
Summaries are generated and may contain mistakes; the official description above is the record.