Skip to main content
CVE-2026-32980VulnerabilityPublished Updated

Openclaw cli: OpenClaw Telegram webhook request bodies were read before secret validation, enabling unauthenticated

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 2026.3.13 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.13
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Upgrade to openclaw version 2026.3.13 or later, which validates the Telegram webhook secret token before reading the request body and rejects unauthorized requests immediately. This fix prevents unauthenticated resource exhaustion attacks on the webhook endpoint.

Description

OpenClaw CLI versions up to 2026.3.12 contain a vulnerability where Telegram webhook request bodies are read and buffered before validating the secret token. This allows unauthenticated attackers to cause resource exhaustion by forcing the server to process large request bodies unnecessarily. The issue is fixed in version 2026.3.13, which performs secret validation before reading the request body.

References

Community reviews

Loading reviews…