openclaw
Affected
- introduced
0, fixed2026.3.13(semver)
Fixed versions
2026.3.13
Fix
- Fixed version
2026.3.13npm install [email protected]
Advisory
Also known as: CVE-2026-32982
OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs
Summaryopenclaw versions <= 2026.3.12 could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed.
Affected Packages / Versions
openclaw (npm)<= 2026.3.122026.3.13Details
The vulnerable path was fetchRemoteMedia() in src/media/fetch.ts. In affected releases, fetch and HTTP error paths embedded the original Telegram file URL into MediaFetchError messages. For Telegram media, those URLs can include /file/bot<TOKEN>/..., so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text.
This issue is in scope under OpenClaw's trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret.
Fix[email protected] redacts sensitive media URLs before constructing fetch error messages. Current code routes the source URL and follow-on error paths through redactMediaUrl() / redactSensitiveText(), so Telegram bot tokens are no longer emitted in those error strings.
Regression coverage exists in src/media/fetch.test.ts (redacts Telegram bot tokens from fetch failure messages and redacts Telegram bot tokens from HTTP error messages).
Fix Commit(s)
7a53eb7ea8295b08be137e231c9a98c1a79b5cd5Thanks @space08 for reporting.
Medium Basis: The source's own band: MODERATE
0, fixed 2026.3.13 (semver)2026.3.13
2026.3.13npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0