Authorization Flaw in openclaw (CVE-2026-41360)
Summary
Vulnerability in openclaw (CVE-2026-41360). Risk of unauthorized operations or information disclosure. Exploitable via openclaw. Mitigation: upgrade to 2026.4.2 or later.
Original description
The description as published by the source.
Summary
Before OpenClaw 2026.4.2, pnpm dlx approval planning did not bind local script operands the same way as related pnpm exec flows. A local script approved through a pnpm dlx path could be replaced before execution without invalidating the approval.
Impact
An operator could approve a benign local script and then execute modified script contents through the still-valid approval plan. This was an approval-integrity bug in the node-host command-planning path.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.4.1 - Patched versions:
>= 2026.4.2 - Latest published npm version:
2026.4.1
Fix Commit(s)
176c059b05357df1bc09d4328a2380670859eeff— bind local scripts inpnpm dlxapproval plans
Release Process Note
The fix is present on main and is staged for OpenClaw 2026.4.2. Publish this advisory after the 2026.4.2 npm release is live.
Thanks @Kazamayc for reporting.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-41360 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.4.2 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41360" on the vendor's site.
CVE-2026-41360 (openclaw) — CWE-863
Attack surface: openclaw / main
Patched: 2026.4.2 — 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.
Incorrect authorization (CWE-863) exists in openclaw. Attackers reach the vulnerable code path via openclaw.
Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw / main.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.4.2.
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.4.2ステージング環境で 2026.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com