Vulnerability in openclaw (CVE-2026-32976)
Summary
Vulnerability in openclaw (CVE-2026-32976). Data can be tampered with by attackers. Exploitable via openclaw. Mitigation: upgrade to 2026.3.11 or later.
Original description
The description as published by the source.
OpenClaw before 2026.3.11 contains an authorization bypass vulnerability allowing channel commands to mutate protected sibling-account configuration despite configWrites restrictions. Attackers with authorized access on one account can execute channel commands like /config set channels..accounts. to modify configuration on target accounts with configWrites: false.
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-32976 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade openclaw to 2026.3.11 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32976" on the vendor's site.
CVE-2026-32976 (openclaw) — CWE-639 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: openclaw / configWrites / channels / operator.admin
Patched: 2026.3.11 — apply immediately
Workaround: Upgrade to 2026.3.11 or later.
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-639) exists in openclaw. Attackers reach the vulnerable code path via openclaw.
Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw / configWrites / channels / operator.admin.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 2026.3.11.
Workaround: Upgrade to 2026.3.11 or later.
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 temporary workaround mitigate
Upgrade to `2026.3.11` or later.パッチが適用されるまでの応急処置として、Upgrade to
2026.3.11or later. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade openclaw to 2026.3.11ステージング環境で 2026.3.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com