GHSA-9VVH-2768-C8VP

In affected versions of openclaw, Discord reaction ingestion for guild channels did not enforce the same member users and roles allowlist checks used for normal inbound guild messages. A non-allowlisted guild member could still trigger reaction events that were accepted and queued as trusted system events for the target session.

Affected Packages and Versions

• Package: openclaw (npm)
• Affected versions: < 2026.3.11
• Fixed in: 2026.3.11

Technical Details

The reaction ingress authorization path enforced DM, group, guild, and channel policy checks, but it did not apply the member-level users and roles allowlist gate that normal guild-message preflight uses. Accepted reactions were then enqueued as trusted system events for the routed session.

Workarounds

Upgrade to 2026.3.11 or later.

This is an authorization bypass in the Discord allowlist path. Reaction text could be injected into downstream session context even when the reacting guild member was not permitted by the configured users or roles allowlist.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

GHSA-9VVH-2768-C8VP has a CVSS score of 5.4 (Medium). The vector is network-reachable, low 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.3.11); upgrading removes the vulnerable code path.

Kodem intelligence

OpenClaw now applies the same users and roles allowlist enforcement to guild reaction ingress that it already applies to normal inbound guild messages. The fix shipped in [email protected].

1. What is GHSA-9VVH-2768-C8VP? GHSA-9VVH-2768-C8VP is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions < 2026.3.11. It is fixed in 2026.3.11. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is GHSA-9VVH-2768-C8VP? GHSA-9VVH-2768-C8VP has a CVSS score of 5.4 (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-9VVH-2768-C8VP? openclaw (npm) versions < 2026.3.11 is affected.
4. Is there a fix for GHSA-9VVH-2768-C8VP? Yes. GHSA-9VVH-2768-C8VP is fixed in 2026.3.11. Upgrade to this version or later.
5. Is GHSA-9VVH-2768-C8VP exploitable, and should I be worried? Whether GHSA-9VVH-2768-C8VP 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-9VVH-2768-C8VP 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-9VVH-2768-C8VP? Upgrade openclaw to 2026.3.11 or later.