OpenClaw's Zalouser allowlist authorization matched mutable group names by default
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-863.
Summary
### 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | openclaw (npm) | before 2026.3.12 | 2026.3.12 | Patch available | GHSA-f5mf-3r52-r83w |
- openclaw (npm) Vendor— Affected before 2026.3.12 Fixed in 2026.3.12 Patch available GHSA-f5mf-3r52-r83w
Remediation
- Fix · GHSA-f5mf-3r52-r83w openclaw (npm) Fixed in 2026.3.12 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f5mf-3r52-r83w
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences