OpenClaw versions 2026.1.30 and below are vulnerable to an authentication bypass that permits attackers to spoof Telegram messages, potentially leading to unauthorized bot actions.

The application fails to perform an authentication check on incoming webhooks when the secret token is not configured. This allows an unauthenticated attacker to inject forged messages into the system by reaching the webhook endpoint.

Successful exploitation allows an attacker to manipulate the bot by spoofing messages from Telegram. Depending on the commands or tools enabled within the OpenClaw environment, this could result in unauthorized administrative actions, data manipulation, or the execution of unintended workflows. Given the CVSS score of 7.5, this vulnerability represents a high risk to service integrity and operational security.

Immediate Action: Update OpenClaw to version 2026.2.1 or later to implement mandatory webhook secret verification.

Proactive Monitoring: Review web server logs for suspicious HTTP POST requests directed at the webhook endpoint from unknown or unexpected IP addresses.

Compensating Controls: If an immediate update is not feasible, ensure that the webhook endpoint is restricted via network access control lists (ACLs) to only accept traffic from known Telegram IP ranges.

Public Exploit Available: No

Administrators currently utilizing Telegram webhook mode should prioritize upgrading to version 2026.2.1 immediately. Because this vulnerability allows for the impersonation of legitimate Telegram traffic, failure to patch could lead to significant unauthorized control over the AI assistant. Ensure that all deployments utilizing the Telegram integration have a secure webhook secret configured as a standard security practice.