Openclaw cli: OpenClaw has a Discord `allowFrom` slug-collision authorization bypass
Affects openclaw-cliSource GCVE Database
CVSS 6.5 Medium : upgrade to 2026.7.1 when convenient.
Data as of 17 Nov 2026, 19:05 UTC
- Patch
- Available – fixed in 2026.7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NWhat to do
Upgrade openclaw-cli to 2026.7.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in openclaw version 2026.2.22 and later. Users should upgrade to this version to mitigate the vulnerability. Additionally, it is recommended to prefer stable Discord user IDs rather than name/tag entries in security-sensitive allowlists. Running the 'openclaw security audit' command will warn about potentially problematic name/tag allowlist entries, which should be addressed where practical.
Description
OpenClaw CLI versions up to 2026.2.21-2 have an authorization bypass vulnerability in Discord allowlists due to slug normalization collisions of user name/tags. This can cause unintended access when different Discord user tags normalize to the same slug, bypassing name-based allowlist checks. The issue is fixed in version 2026.2.22 by preferring resolved user IDs for authorization. Users are advised to prefer stable Discord user IDs in allowlists and run the security audit tool to identify and address warnings.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-4cqv-h74h-93j4 (opens in a new tab)
- github.com/openclaw/openclaw/commit/747bb581b3f2264495e1fec5a0727d9f2ca1b6f1 (opens in a new tab)
- github.com/openclaw/openclaw/commit/f97c45c5b5e0698b6667bb5f6badc0cac7dabd12 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)