Authorization Bypass in OpenClaw: Discord Slug-Collision Vulnerability
Summary
GHSA-4cqv-h74h-93j4: OpenClaw has a Discord allowFrom slug-collision authorization bypass. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.22. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source package designed for integrating Discord functionalities, allowing developers to manage user interactions and permissions effectively. It supports user allowlists based on Discord user IDs or names/tags, enabling fine-grained control over who can access certain features. However, the package has a vulnerability related to how it normalizes user tags, leading to potential authorization bypasses.
Vulnerability Detail
The vulnerability arises from the way OpenClaw normalizes Discord user names and tags into slugs. Different user tags can collide, resulting in multiple tags resolving to the same slug. This can unintentionally allow unauthorized users to gain access to features meant for specific users, as the name-based allowlist entries may be satisfied by these collisions. The issue is particularly concerning in environments where security is paramount, as it could lead to unauthorized access to sensitive functionalities.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.2.22
This is the first release that contains the fix.
npm install openclaw@2026.2.22Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, it is advisable to prefer using stable Discord user IDs for security-sensitive allowlists instead of relying on name/tag entries. This reduces the risk of slug collisions and enhances security.
Conclusion
The OpenClaw package has a significant vulnerability related to Discord slug-collision that can lead to authorization bypasses. It is crucial for developers using this package to update to the latest version and prefer using user IDs for allowlists to enhance security. Regular audits using tools like Vulert can help maintain awareness of potential vulnerabilities.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability is an authorization bypass caused by slug-collision in Discord user name/tag normalization, allowing unauthorized access.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
If an immediate update is not possible, switch to using stable Discord user IDs for allowlists to mitigate the risk.
The CVSS score of this vulnerability is 6.5, indicating a moderate level of severity.
You can find more information about OpenClaw and its functionalities on its official GitHub repository.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
