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-25474
OpenClaw has a Telegram webhook request forgery (missing channels.telegram.webhookSecret) → auth bypass
Summary
In Telegram webhook mode, if channels.telegram.webhookSecret is not set, 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).
Note: Telegram webhook mode is not enabled by default. It is enabled only when channels.telegram.webhookUrl is configured.
Affected Packages / Versions
openclaw (npm)<= 2026.1.30>= 2026.2.1Impact
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.
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:
Thanks @yueyueL for reporting.
High Basis: The source's own band: HIGH
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