Vulnerability in openclaw (CVE-2026-53858)
Summary
Vulnerability in openclaw (CVE-2026-53858). Confidential information can be exposed externally. Exploitable via STATE_DIRECTORY. Mitigation: upgrade to 2026.5.2 or later.
Original description
The description as published by the source.
OpenClaw before 2026.5.2 contains an environment variable injection vulnerability where workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots. Attackers can manipulate the STATE_DIRECTORY variable to load runtime dependencies from unintended local paths, potentially executing malicious code during dependency resolution.
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-53858 has been found in openclaw.
Attackers can target a specific entry point like STATE_DIRECTORY over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.1/10.
What to do: upgrade openclaw to 2026.5.2 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-53858" on the vendor's site.
CVE-2026-53858 (openclaw) — CWE-426 / CVSS v3 7.1
Attack vector: local / unauthenticated
Attack surface: STATE_DIRECTORY
Patched: 2026.5.2 — 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-426) exists in openclaw. Attackers reach the vulnerable code path via STATE_DIRECTORY without authentication.
Check the vendor advisory for the affected versions of openclaw. Attack surface: STATE_DIRECTORY.
Severity: High (CVSS 7.1/10). Confidential information can be exposed externally.
Update to 2026.5.2.
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.5.2ステージング環境で 2026.5.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com