Which versions of Openclaw are affected by CVE-2026-32923?

Organizations using OpenClaw before 2026.3.11 should be aware of moderate risk from CVE-2026-32923, a incorrect authorization vulnerability rated CVSS 5.3.. A patch is available.

How to fix or mitigate CVE-2026-32923?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Openclaw CVE-2026-32923

Q: What is the CVSS score of CVE-2026-32923?

CVE-2026-32923 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-17005 MEDIUM

Incorrect Authorization (CWE-863)

2026-03-29 VulnCheck

Authentication Bypass Openclaw

5.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.11

EUVD ID Assigned

Mar 29, 2026 - 13:15 euvd

EUVD-2026-17005

Analysis Generated

Mar 29, 2026 - 13:15 vuln.today

CVE Published

Mar 29, 2026 - 12:44 nvd

MEDIUM 5.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

3 npm packages depend on openclaw (3 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.3.11.

DescriptionCVE.org

OpenClaw before 2026.3.11 contains an authorization bypass vulnerability in Discord guild reaction ingestion that fails to enforce member users and roles allowlist checks. Non-allowlisted guild members can trigger reaction events accepted as trusted system events, injecting reaction text into downstream session context.

AnalysisAI

OpenClaw before version 2026.3.11 allows authenticated non-allowlisted Discord guild members to bypass authorization checks on reaction ingestion events, enabling them to inject arbitrary reaction text into downstream session context that is trusted as legitimate system events. This authentication-required authorization bypass affects all OpenClaw deployments integrating Discord guild reaction handling and has a CVSS score of 5.3 with confirmed patch availability.

Technical ContextAI

OpenClaw is a Discord integration application that processes guild reaction events. The vulnerability stems from a CWE-863 (Incorrect Authorization) flaw in the reaction ingestion pipeline that fails to validate whether guild members belong to a configured allowlist before accepting their reactions as trusted system events. The authorization bypass permits authenticated Discord users (those with valid credentials) who are not in the allowlisted members or roles to trigger reaction events that are subsequently injected into session context, where they are processed with the same trust level as events from authorized actors. The affected component handles Discord guild reactions, a common integration point for chatbot automation and event processing systems.

RemediationAI

Vendor-released patch: OpenClaw 2026.3.11 or later. Users should immediately upgrade to version 2026.3.11, which restores proper enforcement of member and roles allowlist checks during Discord guild reaction ingestion. Deployment of this patch will reinstate authorization validation and prevent non-allowlisted guild members from injecting reactions into trusted system events. Organizations unable to patch immediately should review Discord guild membership and role assignments to ensure only trusted users are members of the server housing the OpenClaw integration, though this is not a reliable workaround given the authorization bypass nature of the flaw.