Skip to main content
VulnerabilityPublished Updated

CVE-2026-34505: OpenClaw · Zalo webhook rate limiting could be bypassed before secret validation

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2026.3.12 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.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.12
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.12.

Affected software

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

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.12 that applies rate limiting before authentication, closing the pre-auth brute-force gap. Users should update to version 2026.3.12 or later. Additionally, using strong webhook secrets is recommended to reduce the risk of brute-force compromise.

Description

The OpenClaw CLI Zalo webhook handler had a vulnerability where rate limiting was applied only after webhook authentication succeeded. This allowed attackers to bypass rate limiting by sending requests with invalid secrets, facilitating brute-force guessing of webhook secrets. The issue was fixed in version 2026.3.12 by applying rate limiting before authentication. Users should update to this version or later and use strong webhook secrets.

References

Community reviews

Loading reviews…