Privilege Escalation in openclaw (CVE-2026-32051)
Summary
Vulnerability in openclaw (CVE-2026-32051). Risk of unauthorized operations or information disclosure. Exploitable via operator.write. Mitigation: upgrade to 2026.3.1 or later.
Original description
The description as published by the source.
Summary
An authorization mismatch allowed authenticated callers with operator.write access to invoke owner-only tool surfaces (gateway, cron) through agent runs in scoped-token deployments.
Impact
On affected deployments, write-scoped callers could perform control-plane actions beyond intended write scope.
Fix
Owner-only gating is now enforced consistently for owner-only tool surfaces during agent execution, and tool scope classification was tightened to remove the privilege mismatch.
Affected and Patched Versions
- Affected:
<= 2026.2.26 - Patched:
2026.3.1
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-32051 has been found in openclaw.
Attackers can target a specific entry point like operator.write over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.3.1 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32051" on the vendor's site.
CVE-2026-32051 (openclaw) — CWE-269
Attack surface: operator.write / gateway / cron / agent
Patched: 2026.3.1 — 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-269) exists in openclaw. Attackers reach the vulnerable code path via operator.write.
Check the vendor advisory for the affected versions of openclaw. Attack surface: operator.write / gateway / cron / agent.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.3.1.
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.1ステージング環境で 2026.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com