CVE-2026-25474

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.

PUBLISHED Reserved 2026-02-02 | Published 2026-02-19 | Updated 2026-02-19 | Assigner GitHub_M

Problem types

CWE-345: Insufficient Verification of Data Authenticity

Product status

References

github.com/...enclaw/security/advisories/GHSA-mp5h-m6qj-6292

github.com/...ommit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930

github.com/...ommit/5643a934799dc523ec2ef18c007e1aa2c386b670

github.com/...ommit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09

github.com/...ommit/ca92597e1f9593236ad86810b66633144b69314d

github.com/openclaw/openclaw/releases/tag/v2026.2.1

cve.org (CVE-2026-25474)

nvd.nist.gov (CVE-2026-25474)

Download JSON