openclaw
Affected
- introduced
0, fixed2026.2.1(semver)
Fixed versions
2026.2.1
Fix
- Fixed version
2026.2.1npm install [email protected]
Advisory
Also known as: CVE-2026-28454
OpenClaw has a potential access-group authorization bypass if channel type lookup fails
Summary
When Telegram webhook mode is enabled without a configured webhook secret, OpenClaw may accept unauthenticated HTTP POST requests at the Telegram webhook endpoint and trust attacker-controlled update JSON. This can allow forged Telegram updates that spoof message.from.id / chat.id, potentially bypassing sender allowlists and executing privileged bot commands.
Affected Packages / Versions
openclaw (npm)<= 2026.1.30>= 2026.2.1Impact
An attacker who can reach the webhook endpoint can forge Telegram updates and impersonate allowlisted/paired senders by spoofing fields in the webhook payload (for example message.from.id). Impact depends on enabled commands/tools and the deployment’s network exposure.
Mitigations / Workarounds
channels.telegram.webhookSecret and ensure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged.Fix Commit(s)
webhookUrl requires webhookSecret)Defense-in-depth / supporting fixes:
Release Process Note
patched_versions is set to the first fixed release (2026.2.1).
Thanks @yueyueL for reporting.
Critical Basis: The source's own band: CRITICAL
0, fixed 2026.2.1 (semver)2026.2.1
2026.2.1npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0