Path Traversal in openclaw (CVE-2026-44111)
Summary
Path traversal in openclaw (CVE-2026-44111). Risk of unauthorized operations or information disclosure. Exploitable via memory_get. Mitigation: upgrade to 2026.4.15 or later.
Original description
The description as published by the source.
Summary
The QMD backend memory_get read path accepted arbitrary workspace Markdown paths that were inside the workspace but outside the canonical memory locations or indexed QMD result set.
Impact
When the QMD backend was enabled, a caller with access to memory_get could read arbitrary *.md files under the configured workspace root, even when those files were not canonical memory files and had not been returned by QMD search. Severity remains low because exploitation requires access to the memory tool surface and is limited to workspace Markdown files, but it bypassed the intended memory-path policy.
Affected versions
- Affected:
< 2026.4.15 - Patched:
2026.4.15
Fix
OpenClaw 2026.4.15 restricts QMD reads to canonical memory paths or previously indexed QMD workspace paths. Workspace containment alone is no longer sufficient.
Verified in v2026.4.15:
extensions/memory-core/src/memory/qmd-manager.tsrejects non-default workspace Markdown paths unless they match an indexed QMD workspace read path.extensions/memory-core/src/memory/qmd-manager.test.tscovers QMD session search-result reads and the read-path restriction behavior.
Fix commit included in v2026.4.15 and absent from v2026.4.14:
37d5971db36491d5050efd42c333cbe0b98ed292via PR #66026
Thanks to @zsxsoft, Keen Security Lab, and @qclawer for reporting this issue.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-44111 has been found in openclaw.
Attackers can target a specific entry point like memory_get over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.4.15 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-44111" on the vendor's site.
CVE-2026-44111 (openclaw) — CWE-22
Attack surface: memory_get
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.
Path traversal (CWE-22) exists in openclaw. Attackers reach the vulnerable code path via memory_get.
Check the vendor advisory for the affected versions of openclaw. Attack surface: memory_get.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.4.15.
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.4.15ステージング環境で 2026.4.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com