Openclaw cli: OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass (CVE-2026-25474)

OpenClaw CLI versions >=2026.1.29 and <2026.2.1 have an authentication bypass vulnerability (CVE-2026-25474) in Telegram webhook mode if the 'channels.telegram.webhookSecret' is not set. Without this secret, the application does not verify the Telegram secret token header on incoming webhook HTTP requests, allowing attackers who can access the webhook endpoint to send forged Telegram updates. This can lead to unauthorized bot commands or actions depending on the bot's configuration. The vulnerability is fixed in version 2026.2.1 by requiring 'webhookSecret' when 'webhookUrl' is configured and adding runtime guards and other defense-in-depth measures.

Attackers able to reach the Telegram webhook endpoint can send forged updates that the OpenClaw bot processes as legitimate Telegram messages. This can result in unauthorized bot actions, potentially impacting bot integrity and operation. There is no direct impact on confidentiality or availability reported. The severity is high with a CVSS 3.1 score of 7.5 due to the ease of network access and potential for unauthorized command execution.

Apply the official patch by upgrading OpenClaw CLI to version 2026.2.1 or later, which enforces the presence of 'channels.telegram.webhookSecret' when Telegram webhook mode is enabled. Additionally, configure a strong webhook secret and ensure that reverse proxies forward the 'X-Telegram-Bot-Api-Secret-Token' header unchanged. Restrict network access to the webhook endpoint, for example by binding it to the loopback interface and exposing it only via a reverse proxy. These mitigations align with the vendor's advisory and defense-in-depth recommendations.