Authentication Bypass in openclaw (CVE-2026-41362)
Summary
Authentication bypass in openclaw (CVE-2026-41362). Risk of unauthorized operations or information disclosure. Exploitable via event_name. Mitigation: upgrade to 2026.3.31 or later.
Original description
The description as published by the source.
Summary
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.
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.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-41362 has been found in openclaw.
Attackers can target a specific entry point like event_name over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade openclaw to 2026.3.31 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41362" on the vendor's site.
CVE-2026-41362 (openclaw) — CWE-287 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: event_name / message_id / openclaw
Patched: 2026.3.31 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Authentication bypass (CWE-287) exists in openclaw. Attackers reach the vulnerable code path via event_name.
Check the vendor advisory for the affected versions of openclaw. Attack surface: event_name / message_id / openclaw.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2026.3.31.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openclaw' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openclaw' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openclawを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openclaw to 2026.3.31ステージング環境で 2026.3.31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- package github.com
- web github.com
- web github.com
- web github.com