Categories
CVE-2026-53808 medium CVSS 6.5

Vulnerability in openclaw (CVE-2026-53808)

Summary

Vulnerability in openclaw (CVE-2026-53808). Data can be tampered with by attackers. Mitigation: upgrade to 2026.5.6 or later.

Original description

The description as published by the source.

OpenClaw before 2026.5.6 contains an approval policy bypass vulnerability in the Skill Workshop apply flow that allows agent tool calls to set apply: true despite approvalPolicy: pending configuration. Attackers can exploit this by reaching the affected apply path to apply workshop changes before the expected approval step, potentially modifying configurations without proper authorization.

Source: GitHub Security Advisories (Global) 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-53808 has been found in openclaw.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade openclaw to 2026.5.6 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-53808" on the vendor's site.

CVE-2026-53808 (openclaw) — CWE-807 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2026.5.6 — apply immediately
Workaround: set apply: true
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.

❓ What is the problem

A vulnerability (CWE-807) exists in openclaw.

📍 Affected scope

Check the vendor advisory for the affected versions of openclaw.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2026.5.6.

🛡️ Workaround

Workaround: set apply: true

🔍 Detection

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

  1. 1
    Identify exposure identify
    grep -r 'openclaw' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で openclaw を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    set apply: true

    パッチが適用されるまでの応急処置として、set apply: true を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade openclaw to 2026.5.6

    ステージング環境で 2026.5.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm openclaw
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.5.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details