CVE-2026-28454
OpenClaw < 2026.2.2 - Authorization Bypass via Unauthenticated Telegram Webhook
Vexday Risk Score
21Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 8.2EPSS 0.3%KEV nãoPoC —Nuclei —Metasploit —Patch referenciado
Lifecycle
05 Mar 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
OpenClaw · OpenClawWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314dhttps://github.com/openclaw/openclaw/security/advisories/GHSA-fhvm-j76f-qmjvhttps://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-unauthenticated-telegram-webhook