CVE-2026-25474
Authentication Bypass in OpenClaw Telegram Webhook Allows Spoofing
Publication date: 2026-02-19
Last updated on: 2026-02-19
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-345 | The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects OpenClaw, a personal AI assistant, in versions 2026.1.30 and below. When operating in Telegram webhook mode, if the configuration setting channels.telegram.webhookSecret is not set, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header.
As a result, if an attacker can reach the webhook endpoint, they can send forged Telegram updates that OpenClaw will process as if they came from Telegram itself. This can include spoofing the sender's identity (for example, message.from.id).
Because Telegram webhook mode is not enabled by default and only activates when channels.telegram.webhookUrl is configured, this vulnerability only applies in specific deployment scenarios. The issue was fixed in version 2026.2.1.
How can this vulnerability impact me? :
If an attacker can send forged Telegram updates to the vulnerable OpenClaw webhook endpoint, they may cause the bot to perform unintended actions.
The impact depends on the enabled commands, tools, and configuration of the bot. Because the attacker can spoof message senders, they might manipulate the bot into executing commands or actions that it would normally restrict or not perform.
This could lead to unauthorized bot behavior, potentially disrupting services or causing misuse of the bot's capabilities.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade OpenClaw to version 2026.2.1 or later, where the issue has been fixed.
Alternatively, ensure that the configuration parameter channels.telegram.webhookSecret is set when using Telegram webhook mode to enforce verification of Telegram's secret token header.
If Telegram webhook mode is not needed, avoid enabling it by not configuring channels.telegram.webhookUrl.