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

CVE-2026-32035 presents moderate security risk, a incorrect authorization vulnerability rated CVSS 5.9. Attackers could gain access beyond their authorized level.. A patch is available.

How to fix or mitigate CVE-2026-32035?

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-32035

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

CVE-2026-32035 has a CVSS 4.0 base score of 5.8 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/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%.

MEDIUM

Incorrect Authorization (CWE-863)

2026-03-19 disclosure@vulncheck.com

GHSA-wpg9-4g4v-f9rc

Authentication Bypass Openclaw

5.8

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.8 MEDIUM

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/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:H/AT:P/PR:L/UI:A/VC:L/VI:H/VA:L/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

High

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

CVSS changed

Apr 20, 2026 - 13:52 NVD

5.9 (MEDIUM) 5.8 (MEDIUM)

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 19, 2026 - 22:30 vuln.today

CVE Published

Mar 19, 2026 - 22:16 nvd

MEDIUM 5.9

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.2.

DescriptionCVE.org

OpenClaw versions prior to 2026.3.2 fail to pass the senderIsOwner flag when processing Discord voice transcripts in agentCommand, causing the flag to default to true. Non-owner voice participants can exploit this omission to access owner-only tools including gateway and cron functionality in mixed-trust channels.

AnalysisAI

OpenClaw versions prior to 2026.3.2 contain an authorization bypass vulnerability in Discord voice transcript processing where the senderIsOwner flag is not properly validated in the agentCommand handler, causing it to default to true. This allows non-owner participants in mixed-trust Discord channels to gain unauthorized access to owner-only tools including gateway and cron functionality. The vulnerability has a CVSS score of 5.9 (medium severity) with high integrity impact, though real-world exploitation requires user interaction and moderate attack complexity.

Technical ContextAI

The vulnerability stems from improper authorization checks in OpenClaw's Discord voice transcript handler, specifically an instance of CWE-863 (Incorrect Authorization). When processing voice transcripts through the agentCommand function, the application fails to explicitly pass or validate the senderIsOwner authorization flag, allowing it to default to a permissive true value. This represents a classic missing privilege validation flaw in a bot framework designed to integrate with Discord's voice communication channels. The affected technology involves Discord bot command processing where role-based access control should restrict certain operations (gateway and cron tools) to channel owners only, but the absence of flag validation in the transcript processing pathway allows privilege escalation.

RemediationAI

Upgrade OpenClaw to version 2026.3.2 or later, which corrects the senderIsOwner flag validation in the agentCommand voice transcript handler. This patch is available from the official OpenClaw repository. Until patching is completed, implement mitigating controls by restricting voice channel access in Discord servers running OpenClaw to trusted members only, disabling the gateway and cron tools in mixed-trust channels, or temporarily removing non-owner participants from channels where these sensitive tools are exposed. Refer to https://github.com/openclaw/openclaw/security/advisories/GHSA-wpg9-4g4v-f9rc for detailed patch information and deployment guidance.