# CVE-2026-41362: OpenClaw 2026.2.19 through 2026.3.30 - Webhook Replay Dedupe Cache Event Suppression via Shared Authentication

> Attackers can suppress legitimate webhook events on other accounts by exploiting shared cache isolation in multi-account deployments.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Apr 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-6h5h-cp2c-8254, GHSA-fqrj-m88p-qf3v, MINI-5xqq-g73f-9qj6, MINI-74ff-626q-gqxf

## What is CVE-2026-41362?

CVE-2026-41362 is a low-severity vulnerability in Openclaw Openclaw, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2026-41362?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | From 2026.2.19 | 2026.3.31 |
| `openclaw` | npm | From 2026.2.19 | 2026.3.31 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-41362?

Upgrade openclaw to 2026.3.31 or later.

## Is CVE-2026-41362 being exploited?

There is no known exploitation of CVE-2026-41362 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41362 and fix it if it is affected.

What it is: CVE-2026-41362 is a low-severity vulnerability in Openclaw Openclaw, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41362 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected from 2026.2.19; fixed in 2026.3.31
- openclaw (npm): affected from 2026.2.19; fixed in 2026.3.31

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41362/ (Markdown: https://insights.sbomify.com/CVE-2026-41362/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41362
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41362
- OSV: https://osv.dev/vulnerability/CVE-2026-41362

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41362/
Summaries are generated and may contain mistakes; the official description above is the record.