Description
OpenClaw versions prior to 2026.2.2 fail to validate webhook secrets in Telegram webhook mode (must be enabled), allowing unauthenticated HTTP POST requests to the webhook endpoint that trust attacker-controlled JSON payloads. Remote attackers can forge Telegram updates by spoofing message.from.id and chat.id fields to bypass sender allowlists and execute privileged bot commands.
Problem types
Insufficient Verification of Data Authenticity
Product status
Any version before 2026.2.2
Credits
Petr Simecek (@simecek)
Stanislav Fort, Aisle Research, www.aisle.com
References
github.com/...enclaw/security/advisories/GHSA-fhvm-j76f-qmjv (GitHub Security Advisory (GHSA-fhvm-j76f-qmjv))
github.com/...ommit/ca92597e1f9593236ad86810b66633144b69314d (Patch Commit)
github.com/...ommit/5643a934799dc523ec2ef18c007e1aa2c386b670 (Hardening Commit #1)
github.com/...ommit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (Hardening Commit #2)
github.com/...ommit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (Hardening Commit #3)
www.vulncheck.com/...ss-via-unauthenticated-telegram-webhook (VulnCheck Advisory: OpenClaw < 2026.2.2 - Authorization Bypass via Unauthenticated Telegram Webhook)