Skip to content

OpenClaw's Zalouser allowlist authorization matched mutable group names by default

Moderate severity GitHub Reviewed Published Mar 13, 2026 in openclaw/openclaw • Updated Mar 13, 2026

Package

npm openclaw (npm)

Affected versions

<= 2026.3.11

Patched versions

2026.3.12

Description

Summary

OpenClaw's Zalouser allowlist mode accepted mutable group names and normalized slugs as authorization matches instead of requiring stable group IDs. In deployments that used name-based channels.zalouser.groups entries together with permissive sender allowlists, a different group could be accepted by reusing the same display name as an allowlisted group.

Impact

This weakened channel authorization for Zalouser group routing and could allow messages from an unintended group to reach the agent when operators relied on group names instead of stable IDs.

Affected versions

openclaw <= 2026.3.11

Patch

Fixed in openclaw 2026.3.12. Allowlist authorization now matches stable group identifiers, and users should update to 2026.3.12 or later.

References

@steipete steipete published to openclaw/openclaw Mar 13, 2026
Published to the GitHub Advisory Database Mar 13, 2026
Reviewed Mar 13, 2026
Last updated Mar 13, 2026

Severity

Moderate

EPSS score

Weaknesses

Reliance on Untrusted Inputs in a Security Decision

The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. Learn more on MITRE.

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-f5mf-3r52-r83w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.