Vulnerability in openclaw (CVE-2026-32914)
Summary
Vulnerability in openclaw (CVE-2026-32914). Successful exploitation can lead to full system takeover. Exploitable via openclaw. Mitigation: upgrade to 2026.3.12 or later.
Original description
The description as published by the source.
Summary
OpenClaw documented /config and /debug as owner-only commands, but the command handlers checked only whether the sender was command-authorized. A lower-trust sender who was intentionally allowed to run commands could still reach privileged configuration and debugging surfaces.
Impact
This allowed a non-owner sender to read or change privileged configuration that should have remained restricted to owners.
Affected versions
openclaw <= 2026.3.11
Patch
Fixed in openclaw 2026.3.12. Owner checks are now enforced for privileged command surfaces, and regression tests cover /config and /debug access control.
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-32914 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade openclaw to 2026.3.12 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32914" on the vendor's site.
CVE-2026-32914 (openclaw) — CWE-285
Attack vector: remote (network-reachable) / no user interaction
Attack surface: openclaw
Patched: 2026.3.12 — 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-285) exists in openclaw. Attackers reach the vulnerable code path via openclaw.
Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 2026.3.12.
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.12ステージング環境で 2026.3.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com
- web github.com