OpenClaw accepted HTTP requests to the Telegram webhook endpoint without validating the Telegram secret token header when the channels.telegram.webhookSecret configuration was omitted. This missing validation allows an attacker to forge Telegram update messages, such as spoofing the message.from.id field, and have them processed as if they originated from a legitimate Telegram user. Depending on which bot commands or tools are enabled, the forged updates could trigger unintended actions, including sending messages, executing commands, or performing other operations controlled by the AI assistant.

Versions of OpenClaw up to 2026.1.30 are affected. The flaw manifests only when Telegram webhook mode is enabled, which occurs when the channels.telegram.webhookUrl setting is present. All deployments that expose the webhook URL to potential attackers are at risk until the issue is corrected by upgrading to v2026.2.1 or later.

The severity is reflected in a CVSS score of 7.5, while the EPSS score of < 1% indicates a currently low probability of widespread exploitation. The vulnerability is not listed in the CISA KEV catalog. Attackers can exploit the flaw remotely if the webhook endpoint is reachable from the Internet, sending forged HTTP requests that bypass authentication. The flaw is an example of improper validation of critical request data, classified as CWE‑345.