Unauthenticated bot command execution via unsigned webhooks
Published Mar 5, 2026 · Updated Mar 5, 2026
Authorization bypass in OpenClaw before 2026.2.2 allows remote attackers to execute privileged bot commands via forged Telegram updates. The Telegram webhook handler accepts POSTed update JSON without validating a configured secret, then trusts message.from.id and chat.id during allowlist checks. Webhook mode must be enabled without a secret and its endpoint must be reachable; consequences depend on the commands and tools exposed to the bot.
Summary
What happened
Authorization bypass in OpenClaw before 2026.2.2 allows remote attackers to execute privileged bot commands via forged Telegram updates. The Telegram webhook handler accepts POSTed update JSON without validating a configured secret, then trusts message.from.id and chat.id during allowlist checks. Webhook mode must be enabled without a secret and its endpoint must be reachable; consequences depend on the commands and tools exposed to the bot.
The record
- CVE
- CVE-2026-28454
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-285, CWE-345, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo