Skip to content
OpenAdvisories
High · 7.5 CVE-2026-25474 EUVD-2026-8117GHSA-mp5h-m6qj-6292

OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass

Published Feb 19, 2026 · Updated Feb 19, 2026 · Assigned by GitHub_M

Description

OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. In deployments where the webhook endpoint is reachable by an attacker, this can allow forged Telegram updates (for example spoofing message.from.id). If an attacker can reach the webhook endpoint, they may be able to send forged updates that are processed as if they came from Telegram. Depending on enabled commands/tools and configuration, this could lead to unintended bot actions. Note: Telegram webhook mode is not enabled by default. It is enabled only when `channels.telegram.webhookUrl` is configured. This issue has been fixed in version 2026.2.1.

Affected products

VendorProductAffectedFixed
openclaw openclaw < 2026.2.1 —

Affected packages

EcosystemPackageAffectedFixedRecord
npm openclaw < 2026.2.1 2026.2.1 GHSA-mp5h-m6qj-6292

References