OpenClaw: Telegram bot token exposure via logs
Vulnerability
Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include https://api.telegram.org/bot<token>/...). OpenClaw previously logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles.
Impact
Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.14 - Fixed:
>= 2026.2.15(next release)
Mitigation
- Upgrade to
openclaw >= 2026.2.15when released. - Rotate the Telegram bot token if it may have been exposed.
Fix Commit(s)
- cf6990701b258bb9cc4ac7f6c7bdf05016e7f6e46
Thanks @aether-ai-agent for reporting.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | openclaw | < 2026.2.15 | 2026.2.15 |
References
- CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N- Weakness (CWE)
CWE-522- Platform
- npm
- Package
openclaw- Disclosed
- 18.02.2026
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-chf7-jq6g-qrwv - CC BY 4.0
Vulnerability history: openclaw
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 588
- First → latest
- 02.2026 07.2026
- Without a fix
- 9
- Exploited in attacks
- 0
Severity breakdown
- Critical 20
- High 215
- Medium 299
- Low 54
Disclosures per year
- 2026: 588
-
OpenClaw: Telegram bot token exposure via logs this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.