OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
openclawnpm | < 2026.2.1 | 2026.2.1 |
Affected products
2Patches
Vulnerability mechanics
References
8- github.com/advisories/GHSA-mp5h-m6qj-6292ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2026-25474ghsaADVISORY
- github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930ghsax_refsource_MISCWEB
- github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670ghsax_refsource_MISCWEB
- github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09ghsax_refsource_MISCWEB
- github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314dghsax_refsource_MISCWEB
- github.com/openclaw/openclaw/releases/tag/v2026.2.1ghsax_refsource_MISCWEB
- github.com/openclaw/openclaw/security/advisories/GHSA-mp5h-m6qj-6292ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.