Medium

OpenClaw: Zalo webhook rate limiting could be bypassed before secret validation

  • Disclosed: 13.03.2026
  • Updated: 11.10.2026 10:22

Summary

The Zalo webhook handler applied request rate limiting only after webhook authentication succeeded. Requests with an invalid secret returned 401 but did not count against the rate limiter, allowing repeated secret guesses without triggering 429.

Impact

This made brute-force guessing materially easier for weak but policy-compliant webhook secrets. Once the secret was guessed, an attacker could submit forged Zalo webhook traffic.

Affected versions

openclaw <= 2026.3.11

Patch

Fixed in openclaw 2026.3.12. Rate limiting now applies before successful authentication is required, closing the pre-auth brute-force gap. Users should update to 2026.3.12 or later and prefer strong webhook secrets.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package openclaw < 2026.3.12 2026.3.12

References

CVSS score -
CVSS vector
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
Weakness (CWE)
CWE-307
Platform
npm
Package
openclaw
Disclosed
13.03.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-5m9r-p9g7-679c - CC BY 4.0

Vulnerability history: openclaw

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (588) in the archive
Total entries
588
First → latest
02.2026 07.2026
Without a fix
9
Exploited in attacks
0

Severity breakdown

  • Critical 20
  • High 215
  • Medium 299
  • Low 54

Disclosures per year

  1. 2026: 588
Severity:
  1. OpenClaw: Zalo webhook rate limiting could be bypassed before secret validation this entry
    Medium CVE-2026-34505 < 2026.3.12 2026.3.12
  2. High · 8.8 CVE-2026-53811 < 2026.5.7 2026.5.7
  3. High · 8.8 CVE-2026-53806 < 2026.5.12 2026.5.12
  4. High · 7.8 CVE-2026-53813 < 2026.4.25 2026.4.25
  5. High · 7.5 CVE-2026-53834 < 2026.4.27 2026.4.27
  6. Critical CVE-2026-34507 < 2026.4.29 2026.4.29
  7. High CVE-2026-53823 < 2026.5.3 2026.5.3
  8. High · 8.4 CVE-2026-53814 < 2026.5.20 2026.5.20
  9. High · 6.5 CVE-2026-53815 < 2026.5.19 2026.5.19
  10. High · 8.1 CVE-2026-53849 < 2026.5.7 2026.5.7
  11. High · 8.1 CVE-2026-53857 < 2026.5.3 2026.5.3
  12. High · 8.1 CVE-2026-53866 < 2026.5.12 2026.5.12
  13. High · 8.1 CVE-2026-53864 < 2026.5.26 2026.5.26
Show more (20) Showing 41 of 236

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.