OpenClaw: Telegram bot token exposure via logs
CVE-2026-27003 · GHSA-chf7-jq6g-qrwv · published 2026-02-18 · updated 2026-02-20
- Severity
- Medium
- CVSS score
- 6.9
- Chance of exploitation (EPSS)
- 0.16%
- Fixed in
- 2026.2.15
- Exploitation No known exploitation
- Automatable No
- Technical impact Partial
- CISA SSVC
Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access.
Upgrade openclaw to 2026.2.15 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
cf6990701b258bb9cc4ac7f6c7bdf05016e7f6e46 Thanks @aether-ai-agent for reporting.
Upgrade to openclaw >= 2026.2.15 when released. Rotate the Telegram bot token if it may have been exposed.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| openclaw | npm | < 2026.2.15 | 2026.2.15 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- Highn8n: SecurityScorecard Node Leaks API Token to User-Controlled Hostn8n, n8n, n8n
- CriticalOpenClaw: QQBot admin commands could skip DM-only and allowFrom policyopenclaw
- CriticalOpenClaw: Feishu webhook and card-action validation now fail closedopenclaw
- CriticalOpenClaw: Gateway HTTP endpoints re-resolve bearer auth after SecretRef rotationopenclaw
- CriticalOpenClaw: Sandbox escape via TOCTOU race in remote FS bridge readFileopenclaw
- CriticalOpenClaw: Heartbeat context inheritance bypasses sandbox via senderIsOwner escalationopenclaw
- CriticalOpenClaw has a CWD `.env` environment variable injection which bypasses host-env policy and allows config takeoveropenclaw
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.