7.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-25474

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

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.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-25474

CVE-2026-25474:

7.5

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.1	2026.2.1

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability allows an attacker to forge Telegram webhook requests if the channels.telegram.webhookSecret is not configured. This leads to an authentication bypass. The analysis of the provided patches points to the startTelegramWebhook function in src/telegram/webhook.ts as the central point of the vulnerability.

The commit 633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 introduces a runtime guard directly within startTelegramWebhook. It adds a check to ensure that a secret token is provided before proceeding to set up the webhook. If the secret is missing, it throws an error, preventing the application from starting with an insecure webhook configuration. Before this change, the function would happily start the webhook without a secret, and the underlying grammy library would not perform any authentication on incoming requests, creating the vulnerability.

The other commits provide defense-in-depth. ca92597e1f9593236ad86810b66633144b69314d adds configuration validation to prevent such a setup, 5643a934799dc523ec2ef18c007e1aa2c386b670 changes the default listening interface to localhost to reduce network exposure, and 3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 adds request body size limits. While these are important security enhancements, the core logic that allows the insecure behavior at runtime is located in startTelegramWebhook.

Vulnerable functions

startTelegramWebhook

src/telegram/webhook.ts

The vulnerability lies in the `startTelegramWebhook` function, which, prior to the patch, allowed the Telegram webhook to be started without a secret token. The function uses `grammy`'s `webhookCallback` to create a request handler. If the `secretToken` option passed to `webhookCallback` is missing or empty, the handler does not verify the `X-Telegram-Bot-Api-Secret-Token` header in incoming requests. This allows an attacker to send forged webhook requests to the endpoint, bypassing authentication and potentially leading to unauthorized actions. The patch in commit `633fe8b9c17f02fcc68ecdb5ec212a5ace932f09` fixes this by adding a check that throws an error if the secret is missing, thus preventing the webhook server from starting in an insecure configuration.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

7.5

-

Basic Information

Basic Information

Concerned about an active attack path?

CVE-2026-25474: OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass

Summary

Affected Packages / Versions

Impact

Mitigations / Workarounds

Fix Commit(s)

CVE-2026-25474:

7.5

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

CVE-2026-25474: OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth bypass

Summary

Affected Packages / Versions

Impact

Mitigations / Workarounds

Fix Commit(s)

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

7.5

7.5

Technical Details

Basic Information

Basic Information

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI