OpenClaw: Telegram interactive callbacks could skip commands.allowFrom
Affects openclawSource GCVE Database
CVSS 8.8 High : upgrade to 2026.5.6 soon.
Data as of 2 Jul 2026, 23:18 UTC
- Patch
- Available – fixed in 2026.5.6
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:NWhat to do
Upgrade openclaw to 2026.5.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmopenclaw | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.5.6. Operators should upgrade to this version to remediate the vulnerability. Until patched, restrict Telegram command callbacks to trusted chats only. Additionally, narrow channel and tool allowlists, avoid sharing a Gateway between mutually untrusted users, and disable the affected Telegram callback feature if it is not needed.
Description
OpenClaw versions prior to 2026.5.6 contain a vulnerability where Telegram interactive callbacks can bypass the commands.allowFrom sender allowlist. This allows a Telegram user invoking a callback to mark it as an authorized sender before the allowlist check is applied. The vulnerability affects only the Telegram callback feature and does not alter OpenClaw's trusted-operator model. The impact depends on the operator's configuration and whether untrusted input can reach the affected callback path. The issue is patched in version 2026.5.6. Until patched, restricting Telegram command callbacks to trusted chats and narrowing allowlists are recommended mitigations.