En bref
- CVE-2026-25474 est une vulnérabilité ÉLEVÉE (CVSS 7.5) touchant openclaw (openclaw), openclaw.
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.23%, plus élevée que 14.2% des vulnérabilités.
- Correctif : mettre à jour vers 2026.2.1 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| openclaw | < 2026.2.1
| 2026.2.1
|
| openclaw npm | < 2026.2.1
| 2026.2.1
|
Description
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
- Package:
openclaw (npm)
- Affected:
<= 2026.1.30
- Patched:
>= 2026.2.1
Impact
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
- Set a strong
channels.telegram.webhookSecret and ensure your reverse proxy forwards the X-Telegram-Bot-Api-Secret-Token header unchanged.
- Restrict network access to the webhook endpoint (for example bind to loopback and only expose via a reverse proxy).
Fix Commit(s)
- ca92597e1f9593236ad86810b66633144b69314d (config validation:
webhookUrl requires webhookSecret)
Defense-in-depth / supporting fixes:
- 5643a934799dc523ec2ef18c007e1aa2c386b670 (default webhook listener bind host to loopback)
- 3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (bound webhook request body size/time)
- 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (runtime guard: reject webhook startup when secret is missing/empty)
Thanks @yueyueL for reporting.
NVD description
OpenClaw is a personal AI assistant. In versions 2026.1.30 and below, if channels.telegram.webhookSecret is not set when in Telegram webhook mode, 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). 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. Note: Telegram webhook mode is not enabled by default. It is enabled only when `channels.telegram.webhookUrl` is configured. This issue has been fixed in version 2026.2.1.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free