Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-45001 high CVSS 7.1

Vulnerability in openclaw (CVE-2026-45001)

Summary

Vulnerability in openclaw (CVE-2026-45001). Data can be tampered with by attackers. Exploitable via openclaw. Mitigation: upgrade to 2026.4.20 or later.

Original description

The description as published by the source.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Affected versions: < 2026.4.20
  • Patched version: 2026.4.20

Impact

The agent-facing gateway config.patch / config.apply guard did not cover several operator-trusted settings, including sandbox policy, plugin enablement, gateway auth/TLS, hook routing, MCP server configuration, SSRF policy, and filesystem hardening. A prompt-injected model with access to the owner-only gateway tool could persist changes to those settings.

This is a model-to-operator guard bypass, not a remote unauthenticated gateway compromise. Severity is medium.

Fix

OpenClaw now blocks model-driven gateway config mutations for the broader operator-trusted path set and covers per-agent overrides and array-entry patching.

Fix commit:

  • fe30b31a97a917ecc6e92f6c85378b6b20352422

Release

Fixed in OpenClaw 2026.4.20.

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-45001 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade openclaw to 2026.4.20 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-45001" on the vendor's site.

CVE-2026-45001 (openclaw) — CWE-1220 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: openclaw / config.apply / fe30b31a97a917ecc6e92f6c85378b6b20352422
Patched: 2026.4.20 — 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.

❓ What is the problem

A vulnerability (CWE-1220) exists in openclaw. Attackers reach the vulnerable code path via openclaw.

📍 Affected scope

Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw / config.apply / fe30b31a97a917ecc6e92f6c85378b6b20352422.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 2026.4.20.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 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 patch patch 
    Upgrade openclaw to 2026.4.20

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

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

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

Affected packages

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

References

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