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

Not scored Published 3 Mar 2026

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

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	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.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

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.