← Back
CVE-2026-44109
Vulnerability in openclaw (CVE-2026-44109)
Summary
vulnerability in openclaw (CVE-2026-44109). Successful exploitation can lead to full system takeover. Exploitable via ``encryptKey``. Mitigation: upgrade to `2026.4.15` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44109** has been found in openclaw.
Attackers can target a specific entry point like ``encryptKey`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade openclaw to **2026.4.15** or later.
If unsure, ask your IT team or search "openclaw CVE-2026-44109" on the vendor's site.
CVE-2026-44109 (openclaw) — CWE-1188 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `encryptKey` / `c8003f1b33ed2924be5f62131bd28742c5a41aae`
Patched: `2026.4.15` — 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-1188) exists in openclaw. Attackers reach the vulnerable code path via ``encryptKey`` without authentication.
📍 Affected scope
openclaw — . Attack surface: `encryptKey` / `c8003f1b33ed2924be5f62131bd28742c5a41aae`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2026.4.15**.
🛡️ 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.15ステージング環境で 2026.4.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.15"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-44109
- package https://github.com/openclaw/openclaw
- web https://github.com/openclaw/openclaw/security/advisories/GHSA-xh72-v6v9-mwhc
- web https://github.com/openclaw/openclaw/pull/66707
- web https://github.com/openclaw/openclaw/commit/c8003f1b33ed2924be5f62131bd28742c5a41aae
- web https://www.vulncheck.com/advisories/openclaw-authentication-bypass-in-feishu-webhook-and-card-action-validation
- web https://github.com/advisories/GHSA-xh72-v6v9-mwhc