6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-27003

CVE-2026-27003: 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.15 when released.
Rotate the Telegram bot token if it may have been exposed.

Fix Commit(s)

cf6990701b258bb9cc4ac7f6c7bdf05016e7f6e46

Thanks @aether-ai-agent for reporting.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-27003

CVE-2026-27003:

6.9

CVSS Score

4.0

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
openclaw	npm	< 2026.2.15	2026.2.15

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability lies in the unredacted logging of sensitive information, specifically Telegram bot tokens that can appear in error messages or stack traces. The analysis of the provided patch (commit cf69907015b659e5025efb735ee31bd05c4ee3d5) reveals that the openclaw application was not sanitizing error output before logging.

The two key functions responsible for this were formatErrorMessage and formatUncaughtError in src/infra/errors.ts. These functions are used to convert error objects and uncaught exceptions into strings for logging purposes. Before the fix, they returned the raw error details. If an error occurred during a request to the Telegram API, the URL containing the bot token (https://api.telegram.org/bot<token>/...) could be included in the error message or stack trace, which would then be written to the logs.

The patch rectifies this by introducing a call to a new redactSensitiveText function within both formatErrorMessage and formatUncaughtError. This function uses regular expressions, including a new one specifically for Telegram tokens (/\bbot(\d{6,}:[A-Za-z0-9_-]{20,})\b/), to find and mask sensitive data before it is returned for logging. Therefore, these two functions are the direct points in the code where the vulnerability manifested.

Vulnerable functions

formatErrorMessage

src/infra/errors.ts

This function formats error messages for logging. Before the patch, it returned the raw error message, which could contain a sensitive Telegram bot token if an API request failed. The patch added a call to `redactSensitiveText` to sanitize the output before it is logged.

formatUncaughtError

src/infra/errors.ts

This function formats uncaught exceptions, including their stack traces. A Telegram bot token could appear in a stack trace as part of a URL in an error object. The function was modified to pass the stack trace through `redactSensitiveText` to prevent the token from being logged.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.

6.9

-

Basic Information

Basic Information

Concerned about an active attack path?

CVE-2026-27003: OpenClaw: Telegram bot token exposure via logs

Vulnerability

Impact

Affected Packages / Versions

Mitigation

Fix Commit(s)

CVE-2026-27003:

6.9

-

Basic Information

Basic Information

Is this CVE running in your environment?

Technical Details

Technical Details

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability IntelligenceMiggo AI

Unlock WAF rules for this CVE

WAF Protection Rules

WAF Rule

Reasoning

Technical Details

Basic Information

Basic Information

CVE-2026-27003: OpenClaw: Telegram bot token exposure via logs

Vulnerability

Impact

Affected Packages / Versions

Mitigation

Fix Commit(s)

6.9

6.9

Vulnerability IntelligenceMiggo AI

Root Cause Analysis

Vulnerable functions

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI

Vulnerability Intelligence
Miggo AI