← Back
CVE-2026-44995
high
CVSS 7.3
Vulnerability in openclaw (CVE-2026-44995)
Summary
vulnerability in openclaw (CVE-2026-44995). Successful exploitation can lead to full system takeover. Exploitable via ``openclaw``. Mitigation: upgrade to `2026.4.20` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44995** has been found in openclaw.
Attackers can target a specific entry point like ``openclaw`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.3/10.
What to do: upgrade openclaw to **2026.4.20** or later.
If unsure, ask your IT team or search "openclaw CVE-2026-44995" on the vendor's site.
CVE-2026-44995 (openclaw) — CWE-427 / CVSS v3 7.3
Attack vector: local
Attack surface: `openclaw` / `NODE_OPTIONS` / `LD_PRELOAD` / `BASH_ENV`
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-427) exists in openclaw. Attackers reach the vulnerable code path via ``openclaw`` without authentication.
📍 Affected scope
openclaw — . Attack surface: `openclaw` / `NODE_OPTIONS` / `LD_PRELOAD` / `BASH_ENV`.
🔥 Severity
Severity: High (CVSS 7.3/10). Successful exploitation can lead to full system takeover
🔧 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade openclaw to 2026.4.20ステージング環境で 2026.4.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
openclaw
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2026.4.20"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44995
- package https://github.com/openclaw/openclaw
- web https://github.com/openclaw/openclaw/security/advisories/GHSA-mj59-h3q9-ghfh
- web https://github.com/openclaw/openclaw/commit/62fa5071896e95edc7f67d1cebc70a2859e283af
- web https://github.com/openclaw/openclaw/commit/85d86ebc4bf3d2226d39d132a484f4f7a299fa1b
- web https://www.vulncheck.com/advisories/openclaw-arbitrary-code-execution-via-mcp-stdio-environment-variables
- web https://github.com/advisories/GHSA-p3m6-jr2h-hhxj
- web https://github.com/advisories/GHSA-mj59-h3q9-ghfh