Skip to main content
VulnerabilityPublished Updated

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

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.13 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.13
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.13.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.3.13
Fixed in
  • 2026.3.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…