GHSA-f5mf-3r52-r83w

Suggest an improvement
Source
https://github.com/advisories/GHSA-f5mf-3r52-r83w
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-f5mf-3r52-r83w/GHSA-f5mf-3r52-r83w.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-f5mf-3r52-r83w
Downstream
Published
2026-03-13T20:54:00Z
Modified
2026-03-13T22:14:46.983549Z
Summary
OpenClaw's Zalouser allowlist authorization matched mutable group names by default
Details

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.

Database specific 
{
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-13T20:54:00Z",
    "cwe_ids": [
        "CWE-807",
        "CWE-863"
    ],
    "severity": "MODERATE",
    "nvd_published_at": null
}
References

Affected packages

npm / openclaw

Package

Name
openclaw
View open source insights on deps.dev
Purl
pkg:npm/openclaw

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
2026.3.12

Database specific

source 
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/03/GHSA-f5mf-3r52-r83w/GHSA-f5mf-3r52-r83w.json"
last_known_affected_version_range 
"<= 2026.3.11"