PT-2026-20324 · Telegram+1 · Telegram+1

Yueyuel

·

Published

2026-02-17

·

Updated

2026-02-23

·

CVE-2026-25474

CVSS v3.1

7.5

High

VectorAV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Name of the Vulnerable Software and Affected Versions openclaw versions prior to 2026.2.1
Description In Telegram webhook mode, if channels.telegram.webhookSecret is not set, the software may accept webhook HTTP requests without verifying Telegram’s secret token header. This can allow forged Telegram updates, such as spoofing message.from.id, if the webhook endpoint is reachable by an attacker. Telegram webhook mode is not enabled by default and requires configuration of channels.telegram.webhookUrl. An attacker who can reach the webhook endpoint may be able to send forged updates that are processed as if they came from Telegram, potentially leading to unintended bot actions. The vulnerable component is the webhook functionality.
Recommendations versions prior to 2026.2.1: Set a strong channels.telegram.webhookSecret and ensure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged. versions prior to 2026.2.1: Restrict network access to the webhook endpoint. versions prior to 2026.2.1: As a temporary workaround, consider disabling Telegram webhook mode by not configuring channels.telegram.webhookUrl.

Exploit

Fix

Insufficient Verification of Data Authenticity

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-25474
GHSA-MP5H-M6QJ-6292

Affected Products

Telegram
Openclaw