When Telegram webhook mode is enabled without a configured webhook secret, OpenClaw may accept unauthenticated HTTP POST requests at the Telegram webhook endpoint and trust attacker-controlled update JSON. This can allow forged Telegram updates that spoof message.from.id / chat.id, potentially bypassing sender allowlists and executing privileged bot commands.
openclaw (npm)<= 2026.1.30>= 2026.2.1An attacker who can reach the webhook endpoint can forge Telegram updates and impersonate allowlisted/paired senders by spoofing fields in the webhook payload (for example message.from.id). Impact depends on enabled commands/tools and the deployment’s network exposure.
channels.telegram.webhookSecret and ensure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged.webhookUrl requires webhookSecret)Defense-in-depth / supporting fixes:
patched_versions is set to the first fixed release (2026.2.1).
Thanks @yueyueL for reporting.
{
"github_reviewed": true,
"github_reviewed_at": "2026-02-17T21:34:36Z",
"cwe_ids": [
"CWE-285",
"CWE-345"
],
"severity": "CRITICAL",
"nvd_published_at": "2026-03-05T22:16:17Z"
}