openclaw
Affected
- introduced
0, fixed2026.3.11(semver)
Fixed versions
2026.3.11
Fix
- Fixed version
2026.3.11npm install [email protected]
Advisory
Also known as: CVE-2026-32976
OpenClaw: Channel commands could bypass account-scoped configWrites restrictions
Summary
In affected versions of openclaw, channel-initiated config mutations were authorized against the originating account's configWrites policy but did not consistently re-check the targeted account scope. An authorized sender on one account could mutate protected sibling-account configuration when the target account had configWrites: false.
Impact
This is an account-scoped policy bypass inside a single gateway deployment. Channel commands such as /config set channels.<provider>.accounts.<id>... and config-backed /allowlist ... --config --account <id> could modify protected sibling-account configuration.
Affected Packages and Versions
openclaw (npm)<= 2026.3.82026.3.11Technical Details
The mutation path validated the origin account scope but did not consistently authorize every resolved target scope. Ambiguous collection and root writes under channels and channels.<provider>.accounts could therefore reach protected account configuration from channel command surfaces.
Fix
OpenClaw now authorizes config mutations against both the origin scope and each resolved target scope, and it rejects ambiguous root and collection writes from channel commands unless the caller is an internal gateway client with operator.admin. The fix shipped in [email protected].
Workarounds
Upgrade to 2026.3.11 or later.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.3.11 (semver)2026.3.11
2026.3.11npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0