Skip to main content
VulnerabilityPublished Updated

CVE-2026-33580: Openclaw cli · OpenClaw's Nextcloud Talk webhook missing rate limiting on shared secret authentication

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited : upgrade to 2026.3.28 soon.

Data as of 17 Nov 2026, 20:25 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.28

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.28.

Affected software

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

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

AI-suggested

A patch is available and should be applied. The vulnerability is fixed in OpenClaw CLI version 2026.3.28 and later. Users should upgrade to version 2026.3.28 or newer to mitigate this issue.

Description

OpenClaw CLI's Nextcloud Talk webhook lacked rate limiting on signature verification failures, allowing attackers to brute-force weak shared secrets. This could enable forging of inbound webhook events. The vulnerability affects versions from 2026.1.29 up to but not including 2026.3.28. The issue was fixed in version 2026.3.28 by adding throttling on repeated webhook authentication failures.

References

Community reviews

Loading reviews…