Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-chf7-jq6g-qrwv | OpenClaw: Telegram bot token exposure via logs |
Fri, 20 Feb 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| Metrics |
cvssV3_1
|
Fri, 20 Feb 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 20 Feb 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Openclaw
Openclaw openclaw |
|
| Vendors & Products |
Openclaw
Openclaw openclaw |
Thu, 19 Feb 2026 23:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenClaw is a personal AI assistant. Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot<token>/...`). Prior to version 2026.2.15, OpenClaw logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles. Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access. Users should upgrade to version 2026.2.15 to obtain a fix and rotate the Telegram bot token if it may have been exposed. | |
| Title | OpenClaw: Telegram bot token exposure via logs | |
| Weaknesses | CWE-522 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-20T15:37:51.627Z
Reserved: 2026-02-17T03:08:23.489Z
Link: CVE-2026-27003
Updated: 2026-02-20T15:27:00.759Z
Status : Analyzed
Published: 2026-02-20T00:16:16.983
Modified: 2026-02-20T18:06:29.497
Link: CVE-2026-27003
No data.
OpenCVE Enrichment
Updated: 2026-04-17T17:45:24Z
Github GHSA