OpenClaw up to 2026.3.30 Zalo Webhook Replay-Dedupe event_name/message_id exposure of resource
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in OpenClaw up to 2026.3.30. Affected by this issue is some unknown functionality of the component Zalo Webhook Replay-Dedupe Handler. This manipulation of the argument event_name/message_id causes exposure of resource. The identification of this vulnerability is CVE-2026-41362. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.
Details
A vulnerability was found in OpenClaw up to 2026.3.30. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component Zalo Webhook Replay-Dedupe Handler. The manipulation of the argument event_name/message_id with an unknown input leads to a exposure of resource vulnerability. The CWE definition for the vulnerability is CWE-668. The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource. As an impact it is known to affect availability. The summary by CVE is:
OpenClaw versions 2026.2.19 before 2026.3.31 contain an improper cache isolation vulnerability in the Zalo webhook replay-dedupe mechanism that is shared across authenticated webhook targets. Attackers controlling one authenticated Zalo webhook path in multi-account deployments can suppress legitimate events on different accounts by matching event_name and message_id parameters.
The weakness was shared by KeenSecurityLab and qclawer as GHSA-fqrj-m88p-qf3v. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-41362 since 04/20/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2026.3.31 eliminates this vulnerability. Applying the patch 4d038bb242c11f39e45f6a4bde400e5fd42e4ebf is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202604-5557). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 2026.3.0
- 2026.3.1
- 2026.3.2
- 2026.3.3
- 2026.3.4
- 2026.3.5
- 2026.3.6
- 2026.3.7
- 2026.3.8
- 2026.3.9
- 2026.3.10
- 2026.3.11
- 2026.3.12
- 2026.3.13
- 2026.3.14
- 2026.3.15
- 2026.3.16
- 2026.3.17
- 2026.3.18
- 2026.3.19
- 2026.3.20
- 2026.3.21
- 2026.3.22
- 2026.3.23
- 2026.3.24
- 2026.3.25
- 2026.3.26
- 2026.3.27
- 2026.3.28
- 2026.3.29
- 2026.3.30
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exposure of resourceCWE: CWE-668 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: OpenClaw 2026.3.31
Patch: 4d038bb242c11f39e45f6a4bde400e5fd42e4ebf
Timeline
04/20/2026 CVE reserved04/28/2026 Advisory disclosed
04/28/2026 VulDB entry created
04/30/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-fqrj-m88p-qf3v
Researcher: KeenSecurityLab, qclawer
Status: Confirmed
CVE: CVE-2026-41362 (🔒)
GCVE (CVE): GCVE-0-2026-41362
GCVE (VulDB): GCVE-100-359899
CNNVD: CNNVD-202604-5557 - OpenClaw 安全漏洞
Entry
Created: 04/28/2026 06:42Updated: 04/30/2026 03:09
Changes: 04/28/2026 06:42 (80), 04/30/2026 03:09 (6)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.