Authorization Flaw in openclaw (CVE-2026-41350)
Summary
Vulnerability in openclaw (CVE-2026-41350). Risk of unauthorized operations or information disclosure. Exploitable via session_status. Mitigation: upgrade to 2026.3.31 or later.
Original description
The description as published by the source.
Summary
session_status still bypasses configured tools.sessions.visibility for unsandboxed invocations
Current Maintainer Triage
- Status: narrow
- Normalized severity: medium
- Assessment: Real on shipped v2026.3.22: non-sandboxed session_status skipped the shared visibility guard, but this is a same-agent session-policy bypass with unreleased fix, not a broader host-boundary break.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.3.31 - Vulnerable version range:
<=2026.3.28 - Patched versions:
>= 2026.3.31 - First stable tag containing the fix:
v2026.3.31
Fix Commit(s)
4d369a3400dc9b737fbe8daa63f09d909ce7beb8— 2026-03-30T16:48:12+02:00
Release Process Note
- The fix is already present in released version
2026.3.31. - This draft looks ready for final maintainer disposition or publication, not additional code-fix work.
Thanks @tdjackey 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-41350 has been found in openclaw.
Attackers can target a specific entry point like session_status over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.3.31 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41350" on the vendor's site.
CVE-2026-41350 (openclaw) — CWE-863
Attack surface: session_status / tools.sessions.visibility / 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.
Incorrect authorization (CWE-863) exists in openclaw. Attackers reach the vulnerable code path via session_status.
Check the vendor advisory for the affected versions of openclaw. Attack surface: session_status / tools.sessions.visibility / openclaw.
Severity: ?. 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
- package github.com
- web github.com
- web github.com