GHSA-4CQV-H74H-93J4

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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

GHSA-4CQV-H74H-93J4 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.22); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is GHSA-4CQV-H74H-93J4? GHSA-4CQV-H74H-93J4 is a medium-severity improper authentication vulnerability in openclaw (npm), affecting versions <= 2026.2.21-2. It is fixed in 2026.2.22. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is GHSA-4CQV-H74H-93J4? GHSA-4CQV-H74H-93J4 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by GHSA-4CQV-H74H-93J4? openclaw (npm) versions <= 2026.2.21-2 is affected.
4. Is there a fix for GHSA-4CQV-H74H-93J4? Yes. GHSA-4CQV-H74H-93J4 is fixed in 2026.2.22. Upgrade to this version or later.
5. Is GHSA-4CQV-H74H-93J4 exploitable, and should I be worried? Whether GHSA-4CQV-H74H-93J4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-4CQV-H74H-93J4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-4CQV-H74H-93J4? Upgrade openclaw to 2026.2.22 or later.