CVE-2026-32982

Telegram bot token disclosure via unredacted media URLs

Published Mar 31, 2026 · Updated Mar 31, 2026

Information disclosure in OpenClaw before 2026.3.13 allows attackers to obtain Telegram bot tokens through failed inbound media downloads. The fetchRemoteMedia function in src/media/fetch.ts embeds the original Telegram file URL, including its bot-token path segment, in MediaFetchError text without redaction. Exposure requires a configured Telegram integration, a failed inbound download, and access to logs, console output, or another surface that renders the error; the reported consequence is disclosure of the bot token.

CVSS severity8.7
High
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in OpenClaw before 2026.3.13 allows attackers to obtain Telegram bot tokens through failed inbound media downloads. The fetchRemoteMedia function in src/media/fetch.ts embeds the original Telegram file URL, including its bot-token path segment, in MediaFetchError text without redaction. Exposure requires a configured Telegram integration, a failed inbound download, and access to logs, console output, or another surface that renders the error; the reported consequence is disclosure of the bot token.

The record

CVE
CVE-2026-32982
Published
Mar 31, 2026
Updated
Mar 31, 2026
Vendor
OpenClaw Foundation
Product
OpenClaw
Classifications
CWE-532, T1552.001
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Mar 31, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 31, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <2026.3.13

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

OpenClaw Foundation · OpenClawversion=0 <2026.3.13

Published CVSS scores

8.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
7.5VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
6.9GitHubCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-532Insertion of Sensitive Information into Log File
T1552.001Unsecured Credentials: Credentials In Files

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo