GHSA-4cqv-h74h-93j4
OpenClaw has a Discord `allowFrom` slug-collision authorization bypass
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 auditnow warns on Discord name/tag allowlist entries (DM allowlists, guild/channelusers, 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 auditand address warnings where practical.
Fix Commit(s)
- f97c45c5b5e0698b6667bb5f6badc0cac7dabd12
- 747bb581b3f2264495e1fec5a0727d9f2ca1b6f1
OpenClaw thanks @tdjackey for reporting.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
What each source reports
GitHub Advisories Score used 6.5
OpenClaw has a Discord `allowFrom` slug-collision authorization bypass
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 auditnow warns on Discord name/tag allowlist entries (DM allowlists, guild/channelusers, 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 auditand address warnings where practical.
Fix Commit(s)
- f97c45c5b5e0698b6667bb5f6badc0cac7dabd12
- 747bb581b3f2264495e1fec5a0727d9f2ca1b6f1
OpenClaw thanks @tdjackey for reporting.
- Record
GHSA-4cqv-h74h-93j4- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N - Weakness
- CWE-287
- Updated
- 2026-11-02
OSV 6.5
OpenClaw has a Discord `allowFrom` slug-collision authorization bypass
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 auditnow warns on Discord name/tag allowlist entries (DM allowlists, guild/channelusers, 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 auditand address warnings where practical.
Fix Commit(s)
- f97c45c5b5e0698b6667bb5f6badc0cac7dabd12
- 747bb581b3f2264495e1fec5a0727d9f2ca1b6f1
OpenClaw thanks @tdjackey for reporting.
- Record
GHSA-4cqv-h74h-93j4- CVSS 3.1
- 6.5 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N - Weakness
- CWE-287
- Updated
- 2026-11-02
Affected packages
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-4cqv-h74h-93j4 is a medium vulnerability (CVSS 6.5) in openclaw, published March 3, 2026. No source lists public exploit code. Fixed in openclaw 2026.2.22.