CVE-2026-27003: OpenClaw · Telegram bot token exposure via logs
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.2.15 when convenient.
Data as of 19 Nov 2026, 19:34 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.15
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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 18 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.2.15.
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
Upgrade OpenClaw CLI to version 2026.2.15 or later when available. Additionally, rotate any Telegram bot tokens that may have been exposed to prevent unauthorized access.
Description
OpenClaw CLI versions up to 2026.2.14 log Telegram bot tokens in error messages and stack traces without redaction, potentially exposing these tokens in logs, crash reports, CI outputs, or support bundles. This exposure allows attackers to impersonate the bot and gain unauthorized Bot API access. The issue is fixed in version 2026.2.15. Users should upgrade to this version and rotate any potentially exposed Telegram bot tokens.