Which versions of Openclaw are affected by CVE-2026-32982?

OpenClaw versions before 2026.3.13 expose Telegram bot API tokens in error messages, allowing any unauthenticated attacker with network access to harvest credentials through application logs and…. A patch is available.

How to fix or mitigate CVE-2026-32982?

Within 24 hours: Identify all OpenClaw deployments and their current versions via inventory scan; review application logs and error handlers for Telegram token exposure. Within 7 days: Upgrade all OpenClaw instances to version 2026.3.13 or later; rotate all Telegram bot tokens immediately post-upgrade. Within 30 days: audit log aggregation systems (Splunk, ELK, etc.) for historical token exposure; implement log masking rules to prevent credential leakage in future error messages.

Openclaw CVE-2026-32982

Q: What is the CVSS score of CVE-2026-32982?

CVE-2026-32982 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-17385 HIGH

Insertion of Sensitive Information into Log File (CWE-532)

2026-03-31 VulnCheck

Information Disclosure Openclaw

8.7

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

EUVD ID Assigned

Mar 31, 2026 - 11:45 euvd

EUVD-2026-17385

Analysis Generated

Mar 31, 2026 - 11:45 vuln.today

Patch released

Mar 31, 2026 - 11:45 nvd

Patch available

CVE Published

Mar 31, 2026 - 11:17 nvd

HIGH 8.7

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

9 npm packages depend on openclaw (5 direct, 4 indirect)

Ecosystem-wide dependent count for version 2026.3.13.

DescriptionCVE.org

OpenClaw before 2026.3.13 contains an information disclosure vulnerability in the fetchRemoteMedia function that exposes Telegram bot tokens in error messages. When media downloads fail, the original Telegram file URLs containing bot tokens are embedded in MediaFetchError strings and leaked to logs and error surfaces.

AnalysisAI

Telegram bot token exposure in OpenClaw's media download error handling allows unauthenticated remote attackers to harvest sensitive API credentials through information disclosure. Versions prior to 2026.3.13 embed complete Telegram file URLs containing bot tokens in MediaFetchError exceptions, leaking credentials to application logs and error surfaces. With EPSS data unavailable and no CISA KEV listing, no public exploit identified at time of analysis, though the vulnerability requires minimal technical sophistication to exploit given the network-accessible attack vector and low complexity (CVSS:3.1/AV:N/AC:L/PR:N).

Technical ContextAI

This vulnerability stems from improper output neutralization for logs (CWE-532) in OpenClaw's fetchRemoteMedia function, which handles downloads from Telegram's Bot API. Telegram bot tokens are long-lived authentication credentials embedded in file URLs (format: api.telegram.org/file/bot<TOKEN>/<file_path>). When media fetch operations fail, OpenClaw constructs MediaFetchError objects using the raw URL strings without sanitization. The affected component (cpe:2.3:a:openclaw:openclaw) fails to scrub sensitive authentication material before error serialization, causing tokens to persist in application logs, monitoring systems, and potentially user-facing error messages. CWE-532 represents a common but critical oversight where security-sensitive data enters logging pipelines without redaction. Bot tokens provide full API access to the associated Telegram bot account, enabling message interception, user enumeration, and bot impersonation.

RemediationAI

Upgrade immediately to OpenClaw version 2026.3.13 or later, which includes the fix implemented in commit 7a53eb7ea8295b08be137e231c9a98c1a79b5cd5. The patch modifies MediaFetchError construction to sanitize Telegram URLs by removing bot token segments before error message assembly. Organizations unable to upgrade immediately should implement compensating controls: audit all application logs for exposed bot tokens and rotate any discovered credentials through Telegram's BotFather interface, restrict access to application logs and error monitoring systems to authorized personnel only, configure log scrubbing rules to redact patterns matching Telegram bot token formats (regex: bot[0-9]+:[A-Za-z0-9_-]+), and consider temporarily disabling Telegram media fetch functionality if business continuity permits. Post-remediation, perform thorough log review for historical token exposures as leaked credentials may have been harvested prior to patching. Vendor advisory available at https://github.com/openclaw/openclaw/security/advisories/GHSA-xwcj-hwhf-h378 with technical details at commit reference https://github.com/openclaw/openclaw/commit/7a53eb7ea8295b08be137e231c9a98c1a79b5cd5.