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

Organizations using OpenClaw before 2026.3.12 should be aware of notable risk from CVE-2026-32975 rated CVSS 6.9. Exploitation could compromise the security of affected deployments.. A patch is available.

How to fix or mitigate CVE-2026-32975?

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

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

CVE-2026-32975 has a CVSS 4.0 base score of 6.9 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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.1%.

EUVD-2026-17014 MEDIUM

Reliance on Untrusted Inputs in a Security Decision (CWE-807)

2026-03-29 VulnCheck

GHSA-fx9w-r84w-wfmq

Authentication Bypass Openclaw

6.9

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

6.9 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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:N/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

None

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.12

EUVD ID Assigned

Mar 29, 2026 - 13:15 euvd

EUVD-2026-17014

Analysis Generated

Mar 29, 2026 - 13:15 vuln.today

CVE Published

Mar 29, 2026 - 12:44 nvd

MEDIUM 6.9

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.3.12.

DescriptionCVE.org

OpenClaw before 2026.3.12 contains a weak authorization vulnerability in Zalouser allowlist mode that matches mutable group display names instead of stable group identifiers. Attackers can create groups with identical names to allowlisted groups to bypass channel authorization and route messages from unintended groups to the agent.

AnalysisAI

OpenClaw before version 2026.3.12 allows authentication bypass in Zalouser allowlist mode by matching mutable group display names instead of stable identifiers, enabling attackers to create identically-named groups and route messages from unauthorized groups to the agent. The vulnerability requires network access and no authentication, affecting the confidentiality and integrity of message routing with a CVSS score of 6.9. No public exploit code has been identified at time of analysis.

Technical ContextAI

OpenClaw's Zalouser allowlist feature is designed to restrict channel authorization by verifying group membership before routing messages. The vulnerability stems from CWE-807 (Reliance on Untrusted Inputs in a Security Decision), where the authorization logic compares mutable group display names rather than immutable group identifiers. Group display names in Zalouser are user-editable attributes that can be duplicated across different groups, whereas stable group identifiers (typically GUIDs or numeric IDs) uniquely identify groups regardless of display name changes. An attacker can exploit this design flaw by creating a new group with a display name identical to an allowlisted group, causing the authorization check to accept messages from the attacker-controlled group as if they originated from the legitimate allowlisted group. The affected product is identified by CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, indicating all versions prior to 2026.3.12 are vulnerable.

RemediationAI

Upgrade OpenClaw to version 2026.3.12 or later immediately. The patched version implements authorization checks using stable group identifiers instead of mutable display names, preventing name-collision bypass attacks. Users unable to upgrade immediately should audit their Zalouser allowlist configurations to identify groups with identical or suspiciously similar display names and implement manual verification procedures to confirm group identity before routing sensitive messages. Review recent message routing logs to identify any suspicious group activity or unauthorized message flows. Consult the security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-f5mf-3r52-r83w for additional configuration recommendations specific to your deployment.