Vulnerability in openclaw (CVE-2026-41371)
Summary
Vulnerability in openclaw (CVE-2026-41371). Data can be tampered with by attackers. Exploitable via chat.send. Mitigation: upgrade to >= 2026.3.28 or later.
Original description
The description as published by the source.
Summary
The chat.send path reused command authorization to trigger /reset session rotation even though direct session reset is an admin-only control-plane operation.
Impact
A write-scoped gateway caller could rotate a target session, archive the prior transcript state, and force a new session id without admin scope.
Affected Component
src/gateway/server-methods/chat.ts, src/auto-reply/reply/session.ts
Fixed Versions
- Affected:
<= 2026.3.24 - Patched:
>= 2026.3.28 - Latest stable
2026.3.28contains the fix.
Fix
Fixed by commit be00fcfccb (Gateway: align chat.send reset scope checks).
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-41371 has been found in openclaw.
Attackers can target a specific entry point like chat.send over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 8.5/10.
What to do: upgrade openclaw to >= 2026.3.28 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-41371" on the vendor's site.
CVE-2026-41371 (openclaw) — CWE-284 / CVSS v3 8.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: chat.send / be00fcfccb
Patched: >= 2026.3.28 — 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.
A vulnerability (CWE-284) exists in openclaw. Attackers reach the vulnerable code path via chat.send.
Check the vendor advisory for the affected versions of openclaw. Attack surface: chat.send / be00fcfccb.
Severity: High (CVSS 8.5/10). Data can be tampered with by attackers.
Update to >= 2026.3.28.
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.28ステージング環境で >= 2026.3.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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