← Back
CVE-2026-41365
Authorization Flaw in openclaw (CVE-2026-41365)
Summary
vulnerability in openclaw (CVE-2026-41365). Risk of unauthorized operations or information disclosure. Exploitable via ``openclaw``. Mitigation: upgrade to `2026.3.31` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41365** 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. CVSS score: ?/10.
What to do: upgrade openclaw to **2026.3.31** or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41365" on the vendor's site.
CVE-2026-41365 (openclaw) — CWE-863 /
Attack surface: `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.
❓ What is the problem
**incorrect authorization** (CWE-863) exists in openclaw. Attackers reach the vulnerable code path via ``openclaw`` without authentication.
📍 Affected scope
openclaw — . Attack surface: `openclaw`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2026.3.31**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openclaw to 2026.3.31ステージング環境で 2026.3.31 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
openclaw
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.3.31"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-41365
- package https://github.com/openclaw/openclaw
- web https://github.com/openclaw/openclaw/security/advisories/GHSA-chfm-xgc4-47rj
- web https://github.com/openclaw/openclaw/commit/5cca38084074fb5095aa11b6a59820d63e4937c9
- web https://github.com/openclaw/openclaw/releases/tag/v2026.3.31
- web https://www.vulncheck.com/advisories/openclaw-sender-allowlist-bypass-via-graph-api-thread-history
- web https://github.com/advisories/GHSA-chfm-xgc4-47rj