Staging Environment: Content and features may be unstable or change without notice.
Advisory details: github_osv / GHSA-mp5h-m6qj-6292
Advisory ID github_osv/GHSA-mp5h-m6qj-6292
Aliases CVE-2026-25474
Summary 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.
Status Published
Exploitability 0.5
Weighted Severity 6.8
Risk 3.4
Affected and Fixed Packages Package Details
Introduced and Fixed Package Commit Patches Package Commit Patches Details
Weaknesses (1)
CWE-345 Insufficient Verification of Data Authenticity
System Score Found at
cvssv3.1 7.5 https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-mp5h-m6qj-6292/GHSA-mp5h-m6qj-6292.json
generic_textual HIGH
Reference id Reference type URL
https://github.com/openclaw/openclaw
https://github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930
https://github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670
https://github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09
https://github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d
https://github.com/openclaw/openclaw/releases/tag/v2026.2.1
CVE-2026-25474 https://nvd.nist.gov/vuln/detail/CVE-2026-25474
GHSA-mp5h-m6qj-6292 https://github.com/openclaw/openclaw/security/advisories/GHSA-mp5h-m6qj-6292
No exploits are available.

No EPSS data available for this advisory.

Patch URL
There are no known patches.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Found at https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/02/GHSA-mp5h-m6qj-6292/GHSA-mp5h-m6qj-6292.json
Attack Vector (AV) Attack Complexity (AC) Privileges Required (PR) User Interaction (UI) Scope (S) Confidentiality Impact (C) Integrity Impact (I) Availability Impact (A)

network

adjacent_network

local

physical

low

high

none

low

high

none

required

unchanged

changed

high

low

none

high

low

none

high

low

none

Vector: SSVCv2/E:N/A:Y/T:P/P:M/B:A/M:M/D:T/2026-02-19T17:23:26Z/

Decision: Track

Source URL: https://github.com/cisagov/vulnrichment/blob/develop/2026/25xxx/CVE-2026-25474.json

Source Advisory: vulnrichment/CVE-2026-25474

View SSVC decision tree 
[{'Exploitation': 'none'},
 {'Automatable': 'yes'},
 {'Technical Impact': 'partial'},
 {'Mission Prevalence': 'minimal'},
 {'Public Well-being Impact': 'material'},
 {'Mission & Well-being': 'medium'}]