Skip to main content
EPSS 0.5%top 59%

Openclaw cli: OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs (CVE-2026-32982)

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

Description

OpenClaw CLI versions up to 2026.3.12 could leak Telegram bot tokens in error messages when media fetches failed. This occurs because error strings included raw Telegram file URLs containing bot tokens. The issue was fixed in version 2026.3.13 by redacting sensitive tokens from error messages.

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.3.13

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, 12:58:30 UTC

Technical Analysis

The vulnerability in openclaw CLI (<= 2026.3.12) involves the exposure of Telegram bot tokens in error messages generated during failed media fetch operations. Specifically, the fetchRemoteMedia() function embedded Telegram file URLs, which contain bot tokens, into MediaFetchError messages. These tokens could then be exposed in logs, console outputs, or any downstream error handling that rendered these messages. The fix in version 2026.3.13 introduces redaction of sensitive tokens from these URLs before constructing error messages, preventing token leakage.

Potential Impact

Telegram bot tokens used by OpenClaw integrations could be exposed in logs or error outputs, potentially allowing unauthorized access to the bot if logs or error messages are accessible. This exposure is limited to OpenClaw-operated credentials and does not involve user-supplied secrets.

Mitigation Recommendations

A fix is available in openclaw version 2026.3.13 which redacts Telegram bot tokens from media fetch error messages. Users should upgrade to this version or later to prevent token leakage. No additional mitigation is required as the issue is resolved by the official patch.

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-32982
Osv Schema Version
1.7.3
Ecosystems
["Homebrew"]
Cvss Version
4.0

Threat ID: 6ac245b312601ec6a3166b36

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

Last enriched: 10/04/2026, 12:58:30 UTC

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

Views: 2

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