CVE-2026-25474

The record

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 packages

Related vulnerabilities

• GHSA-mp5h-m6qj-6292 OpenClaw has a Telegram webhook request forgery (missing… Same vulnerability
• GHSA-4hpg-mp64-x7xq OpenClaw: Internal/webchat command auth could inherit ownerAllowFrom wildcard state Also affects openclaw
• GHSA-8mg9-j9cf-54cj OpenClaw: Empty-scope device re-pairing could confuse caller scope containment Also affects openclaw
• GHSA-rx78-29qr-5hq8 OpenClaw: Workspace-derived service PATH could influence trash command selection Also affects openclaw
• GHSA-wc84-j36w-pw4x OpenClaw: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots Also affects openclaw
• GHSA-cw4q-gqg5-g38h OpenClaw: Discord allowFrom could bind to mutable display names Also affects openclaw
• GHSA-mpc8-jxjh-qpgh OpenClaw: Focus command could miss controlScope enforcement Also affects openclaw
• GHSA-24vr-rprv-67rf OpenClaw: Workspace .env npm_execpath could influence bundled runtime dependency install Also affects openclaw