Summary
OpenClaw: Zalo replay dedupe cache could suppress events across authenticated webhook targets
Before OpenClaw 2026.3.31, the Zalo webhook replay-dedupe cache was shared across authenticated webhook targets and keyed too broadly. In multi-account deployments, a replay seen on one account could suppress a legitimate event on another account if event_name and message_id matched.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
>= 2026.2.19, < 2026.3.31 - Patched versions:
>= 2026.3.31 - Latest published npm version:
2026.4.1
Fix Commit(s)
4d038bb242c11f39e45f6a4bde400e5fd42e4ebf, scope webhook replay dedupe per target7cea7c29705b188b464cc9cdc107c275b94b2a72, follow-up hardening to scope replay dedupe by path and account
Release Process Note
The initial fix shipped in OpenClaw 2026.3.31 on March 31, 2026. The current published npm release 2026.4.1 from April 1, 2026 also contains follow-up hardening for the same surface.
Thanks @nexrin for reporting.
Impact
An attacker who controlled one authenticated Zalo webhook path in a multi-account gateway deployment could cause silent message suppression on a different Zalo account sharing that gateway. This was an availability issue; it did not provide cross-account authentication or data access.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-FQRJ-M88P-QF3V? GHSA-FQRJ-M88P-QF3V is a low-severity improper authentication vulnerability in openclaw (npm), affecting versions >= 2026.2.19, < 2026.3.31. It is fixed in 2026.3.31. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of openclaw are affected by GHSA-FQRJ-M88P-QF3V? openclaw (npm) versions >= 2026.2.19, < 2026.3.31 is affected.
- Is there a fix for GHSA-FQRJ-M88P-QF3V? Yes. GHSA-FQRJ-M88P-QF3V is fixed in 2026.3.31. Upgrade to this version or later.
- Is GHSA-FQRJ-M88P-QF3V exploitable, and should I be worried? Whether GHSA-FQRJ-M88P-QF3V is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-FQRJ-M88P-QF3V is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-FQRJ-M88P-QF3V? Upgrade
openclawto 2026.3.31 or later.