Openclaw cli: OpenClaw has a Telegram webhook request forgery (missing `channels.telegram.webhookSecret`) → auth
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 2026.2.1 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official patch by upgrading OpenClaw CLI to version 2026.2.1 or later, which enforces the presence of 'channels.telegram.webhookSecret' when Telegram webhook mode is enabled. Additionally, configure a strong webhook secret and ensure that reverse proxies forward the 'X-Telegram-Bot-Api-Secret-Token' header unchanged. Restrict network access to the webhook endpoint, for example by binding it to the loopback interface and exposing it only via a reverse proxy. These mitigations align with the vendor's advisory and defense-in-depth recommendations.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.1 have a vulnerability in Telegram webhook mode where missing the configuration of 'channels.telegram.webhookSecret' allows acceptance of webhook HTTP requests without verifying Telegram's secret token header. This can enable attackers who can reach the webhook endpoint to send forged Telegram updates, potentially causing unintended bot actions. Telegram webhook mode is not enabled by default and requires explicit configuration. A patch is available in version 2026.2.1 and later.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-mp5h-m6qj-6292 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-25474 (opens in a new tab)
- github.com/openclaw/openclaw/commit/3cbcba10cf30c2ffb898f0d8c7dfb929f15f8930 (opens in a new tab)
- github.com/openclaw/openclaw/commit/5643a934799dc523ec2ef18c007e1aa2c386b670 (opens in a new tab)
- github.com/openclaw/openclaw/commit/633fe8b9c17f02fcc68ecdb5ec212a5ace932f09 (opens in a new tab)
- github.com/openclaw/openclaw/commit/ca92597e1f9593236ad86810b66633144b69314d (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.1 (opens in a new tab)