CVE-2026-53837: OpenClaw: Mattermost handlers could fall open when channel type was missing

OpenClaw applies a direct-message policy to Mattermost events. That policy depends on knowing the channel type. In affected versions, an event with no channel type metadata did not get the policy check. The handler carried on and processed the event. This is a fail-open error (CWE-636). The sources do not name the specific handler or the missing validation.

An attacker needs network access and a way to get a crafted or malformed Mattermost event to the Gateway. The CVSS vector rates attack complexity as high, requires no privileges or user interaction, and rates integrity impact as low, with no confidentiality or availability impact. The result is that content which should have been blocked by channel policy gets processed by the agent. What that means depends on which tools the agent can use and whether lower-trust users can reach the Mattermost bot.

The advisory says OpenClaw's trusted-operator model is unchanged. Authenticated operators and installed plugins stay trusted.

Affected: npm openclaw up to and including 2026.5.5. Only setups with the Mattermost integration enabled and reachable are exposed.

npm ls -g openclaw

Drop -g for a project install. Check your Gateway configuration for a Mattermost channel and for who can message the bot.

Update to openclaw 2026.5.6, the first stable patched version.

npm install -g [email protected]

Until you can update, the advisory advises keeping Mattermost bot access restricted and reviewing channel metadata errors. It also suggests narrow channel and tool allowlists, not sharing one Gateway between mutually untrusted users, and disabling the Mattermost feature if you do not need it.

Review Gateway logs for Mattermost events that carry no channel type, and for errors about missing channel metadata, which the advisory tells you to review. Look for DM-policy-gated users or channels whose messages were processed when policy should have blocked them. Check Mattermost bot activity for messages from accounts outside your allowlist.

Summary

Mattermost handlers could fall open when channel type was missing. In affected versions, a Mattermost event missing channel type metadata could continue without applying the intended DM policy decision.

This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed.

Impact

When the affected feature is enabled and reachable, this could process a Mattermost event that should have been gated by channel policy. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path.

Patched Versions

The first stable patched version is 2026.5.6.

Mitigations

keep Mattermost bot access restricted and review channel metadata errors until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.