Skip to main content
EPSS 0.2%top 96%

Openclaw cli: OpenClaw: Telegram bot token exposure via logs (CVE-2026-27003)

0
High
Published: 08/13/2026 (08/13/2026, 17:21:32 UTC)
Source: GCVE Database
Product: openclaw-cli

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.

CVSS v4.0

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

Homebrewmore threats →ghsa
openclaw-cli
pkg:brew/openclaw-cli
Affected versions
>=2026.1.29 <2026.2.15

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/04/2026, 13:13:07 UTC

Technical Analysis

OpenClaw CLI versions <= 2026.2.14 log Telegram bot tokens in error messages and stack traces, including request URLs containing the token. This logging occurs without redaction, risking token exposure in various outputs such as logs and crash reports. Disclosure of the Telegram bot token enables attackers to impersonate the bot and take over Bot API access. The vulnerability is addressed in OpenClaw CLI version >= 2026.2.15.

Potential Impact

Exposure of Telegram bot tokens can lead to unauthorized access and control over the bot via the Bot API, allowing attackers to impersonate the bot. This compromises the confidentiality and integrity of the bot's operations.

Mitigation Recommendations

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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BREW-openclaw-cli-CVE-2026-27003
Osv Schema Version
1.7.3
Ecosystems
["Homebrew"]
Cvss Version
4.0

Threat ID: 6ac245ce12601ec6a3167fd6

Added to database: 10/04/2026, 12:25:50 UTC

Last enriched: 10/04/2026, 13:13:07 UTC

Last updated: 10/04/2026, 16:08:37 UTC

Views: 1

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses