Authorization Flaw in OpenClaw (CVE-2026-100552)
Summary
Vulnerability in OpenClaw (CVE-2026-100552). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2026.8.1 or later.
Original description
The description as published by the source.
OpenClaw (npm package 'openclaw') before 2026.8.1 does not correctly enforce per-chat tool policies for Codex app-server runtime tools. A conversation-level tools.allow rule filtered OpenClaw tools but did not restrict the shell, process, file, and patch tools owned by the Codex runtime. When a lower-trust conversation was assigned to a Codex runtime and restricted with a per-chat tool allowlist, a participant able to trigger that agent could still reach native command and file tools, bypassing the configured allowlist. The practical impact depends on the runtime's host permissions and sandbox configuration. The issue is fixed in 2026.8.1.
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-100552 has been found in OpenClaw.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade OpenClaw to 2026.8.1 or later.
If unsure, ask your IT team or search "OpenClaw CVE-2026-100552" on the vendor's site.
CVE-2026-100552 (OpenClaw) — CWE-863 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 2026.8.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.
Incorrect authorization (CWE-863) exists in OpenClaw.
Check the vendor advisory for the affected versions of OpenClaw.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 2026.8.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.8.1ステージング環境で 2026.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com