Authorization Flaw in openclaw (CVE-2026-32972)
Summary
Vulnerability in openclaw (CVE-2026-32972). Data can be tampered with by attackers. Exploitable via operator.write. Mitigation: upgrade to 2026.3.11 or later.
Original description
The description as published by the source.
Summary
An authorization mismatch in the gateway let an authenticated caller with only operator.write use browser.request to reach browser profile management routes that persist configuration to disk. In practice, this exposed an admin-only configuration write primitive through /profiles/create.
Impact
A write-scoped operator could create or modify browser profiles and store attacker-chosen remote CDP endpoints without holding operator.admin.
Affected versions
openclaw <= 2026.3.8
Patch
Fixed in openclaw 2026.3.11 and included in later releases such as 2026.3.12. Browser profile creation now requires the correct admin boundary, and regression tests cover the write-vs-admin authorization split.
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-32972 has been found in openclaw.
Attackers can target a specific entry point like operator.write over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade openclaw to 2026.3.11 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32972" on the vendor's site.
CVE-2026-32972 (openclaw) — CWE-863
Attack vector: remote (network-reachable) / no user interaction
Attack surface: operator.write / browser.request / operator.admin / openclaw
Patched: 2026.3.11 — 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.
Incorrect authorization (CWE-863) 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 / browser.request / operator.admin / openclaw.
Severity: ?. Data can be tampered with by attackers.
Update to 2026.3.11.
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.11ステージング環境で 2026.3.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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