OpenClaw Telegram webhook secret validation bypass (CVE-2026-25474)
OpenClaw versions up to 2026.1.30 could accept Telegram webhook requests without verifying a secret token if the webhookSecret configuration parameter was not set, potentially allowing attackers who can reach the endpoint to forge Telegram updates. The vulnerability was patched in version 2026.2.1.
What happened
In OpenClaw's Telegram webhook mode, if the configuration parameter channels.telegram.webhookSecret is not set, the application may accept webhook HTTP requests without verifying Telegram's secret token header.
Telegram webhook mode is not enabled by default and is only activated when channels.telegram.webhookUrl is configured. Affected versions are OpenClaw up to 2026.1.30; the issue was patched in version 2026.2.1.
Reported impact
If an attacker can reach the webhook endpoint, they may send forged updates that are processed as if they came from Telegram. Depending on enabled commands and configuration, this could lead to unintended bot actions.
Index analysis
The vulnerability received a CVSS v3 base score of 7.5 (High), with attack vector network, attack complexity low, and no privileges or user interaction required.
Governance controls
The fix enforces bounded webhook body handling and includes runtime guards to reject webhook startup when the secret is missing or empty. Supporting fixes default the webhook listener bind host to loopback address.
Classification
Sources and evidence
This record was researched and written by the Index, based on the following original reporting.