GHSA-w5ww-7chg-mxcq: OpenClaw: Telegram interactive callbacks could skip commands.allowFrom
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.
AI Analysis
Technical Summary
In OpenClaw versions before 2026.5.6, a vulnerability exists in the Telegram interactive callback feature where the commands.allowFrom sender allowlist can be bypassed. A Telegram user able to invoke an affected callback can mark the callback as an authorized sender prior to the allowlist enforcement, potentially triggering command behavior outside the configured allowlist. This vulnerability is scoped to the Telegram callback feature and does not affect the overall trusted-operator security model of OpenClaw. The practical impact depends on the operator's configuration and exposure of the affected feature to lower-trust inputs. The vulnerability is addressed in OpenClaw version 2026.5.6.
Potential Impact
When the vulnerable Telegram callback feature is enabled and accessible, commands may execute for Telegram users outside the configured allowlist, potentially allowing unauthorized command execution. The actual risk depends on the operator's configuration and whether untrusted Telegram users can reach the affected callback. The vulnerability does not affect other trusted components or the general operator trust model.
Mitigation Recommendations
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.
GHSA-w5ww-7chg-mxcq: OpenClaw: Telegram interactive callbacks could skip commands.allowFrom
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.
CVSS v4.0
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In OpenClaw versions before 2026.5.6, a vulnerability exists in the Telegram interactive callback feature where the commands.allowFrom sender allowlist can be bypassed. A Telegram user able to invoke an affected callback can mark the callback as an authorized sender prior to the allowlist enforcement, potentially triggering command behavior outside the configured allowlist. This vulnerability is scoped to the Telegram callback feature and does not affect the overall trusted-operator security model of OpenClaw. The practical impact depends on the operator's configuration and exposure of the affected feature to lower-trust inputs. The vulnerability is addressed in OpenClaw version 2026.5.6.
Potential Impact
When the vulnerable Telegram callback feature is enabled and accessible, commands may execute for Telegram users outside the configured allowlist, potentially allowing unauthorized command execution. The actual risk depends on the operator's configuration and whether untrusted Telegram users can reach the affected callback. The vulnerability does not affect other trusted components or the general operator trust model.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-w5ww-7chg-mxcq
- Osv Schema Version
- 1.4.0
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a46ecc527e9c7971943d833
Added to database: 07/02/2026, 22:57:09 UTC
Last enriched: 07/02/2026, 23:18:21 UTC
Last updated: 07/02/2026, 23:18:21 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.