OpenClaw versions before 2026.2.2 do not validate webhook secrets when Telegram webhook mode is enabled, allowing attackers to send unauthenticated HTTP POST requests that the application accepts as legitimate Telegram updates. By forging the message.from.id and chat.id fields in the payload, an attacker can bypass sender allowlists and execute privileged bot commands, effectively achieving an authorization bypass.

The vulnerability affects installations of the OpenClaw application running on Node.js environments where the Telegram webhook mode is enabled. Any deployment using OpenClaw before the 2026.2.2 release is subject to this issue.

The CVSS score of 8.2 indicates a high-severity flaw, although the EPSS score of less than 1% suggests that exploitation is presently rare. The vulnerability is not listed in the CISA KEV catalog. Remote attackers can exploit the flaw by sending unauthenticated HTTP POST requests directly to the webhook endpoint; this is inferred from the description as the application would accept and process the payload without requiring authentication.