CVE-2026-25474: OpenClaw Telegram Webhook Request Forgery Leading to Auth Bypass
Summary
CVE-2026-25474: In Telegram webhook mode, if channels.telegram.webhookSecret is not set, OpenClaw may accept webhook HTTP requests without verifying Telegram’s secret token header. Affects openclaw versions < 2026.2.1. Fixed in 2026.2.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source framework designed for building Telegram bots. It allows developers to create interactive and automated experiences on the Telegram platform. One of its key features is the ability to receive updates via webhooks, which are HTTP callbacks triggered by events in Telegram. However, if not properly configured, OpenClaw can be vulnerable to unauthorized access due to a missing webhook secret.
Vulnerability Detail
The vulnerability arises when the channels.telegram.webhookSecret is not set in OpenClaw's configuration. In this scenario, the application may accept webhook requests without verifying the Telegram secret token header. This flaw can be exploited by an attacker who can reach the webhook endpoint, allowing them to send forged updates that the bot processes as legitimate messages from Telegram. The potential ramifications include unauthorized bot actions, which can lead to data leaks or unintended interactions with users.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.2.1
This is the first release that contains the fix.
npm install openclaw@2026.2.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can restrict network access to the webhook endpoint by binding it to the loopback interface. This can be achieved by modifying your server configuration to only allow local connections. For example, if using Express.js, you can set the server to listen on localhost:
const express = require('express');
const app = express();
app.listen(3000, '127.0.0.1'); // Only accessible from localhost
Conclusion
The CVE-2026-25474 vulnerability in OpenClaw poses a significant risk due to the potential for unauthorized access via forged Telegram updates. It is crucial to update to the patched version and implement security best practices to mitigate this risk.
See every vulnerability recorded for openclaw →
FAQ
An attacker can send forged updates to the bot, potentially leading to unauthorized actions and data exposure.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
No, the Telegram webhook mode is not enabled by default. It is only activated when channels.telegram.webhookUrl is configured.
In the meantime, ensure that the webhook endpoint is only accessible from trusted sources by restricting network access.
The CVSS score for this vulnerability is 7.5, indicating a high severity level.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
