Skip to main content
CVE-2026-28461VulnerabilityPublished Updated

Openclaw cli: OpenClaw has unbounded memory growth in Zalo webhook via query-string key churn (unauthenticated DoS)

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.1 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 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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.1.

Affected software

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

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 in OpenClaw CLI version 2026.3.1 that addresses this vulnerability by normalizing webhook tracking keys and bounding the tracking state to prevent unbounded memory growth. Users should upgrade to version 2026.3.1 or later to remediate this issue.

Description

OpenClaw CLI versions up to 2026.2.26 have an unauthenticated denial-of-service vulnerability in the Zalo webhook endpoint. Attackers can cause unbounded memory growth by sending requests with varying query-string keys to the same webhook path, leading to potential process instability or out-of-memory conditions. This issue is fixed in version 2026.3.1 by normalizing keys and bounding the tracking state to prevent unbounded growth.

References

Community reviews

Loading reviews…