Path Traversal in openclaw (CVE-2026-3689)
Summary
Path traversal in openclaw (CVE-2026-3689). Risk of unauthorized operations or information disclosure. Exploitable via POST /tools/invoke. Mitigation: upgrade to 2026.2.21 or later.
Original description
The description as published by the source.
ZDI-CAN-29312: OpenClaw Canvas Path Traversal Information Disclosure Vulnerability
-- ABSTRACT -------------------------------------
Trend Micro's Zero Day Initiative has identified a vulnerability affecting the following products:
OpenClaw - OpenClaw
-- VULNERABILITY DETAILS ------------------------
- Version tested: openclaw 2026.2.17
- Platform tested: macOS 26.3
Analysis
Description
The OpenClaw gateway's canvas tool accepts an a2ui_push action with a jsonlPath parameter that specifies a filesystem path to read. The gateway reads this file using fs.readFile() with no path validation, canonicalization, or directory restriction. An authenticated attacker can supply an arbitrary absolute or relative path to read any file accessible to the gateway process.
The file contents are forwarded to the connected node client via the canvas.a2ui.pushJSONL WebSocket command. The gateway itself returns { ok: true } to the HTTP caller, confirming the file was read and transmitted.
Root Cause
In src/agents/tools/canvas-tool.ts, the a2ui_push action handler reads a file from disk without any path restrictions:
case "a2ui_push": {
const jsonl =
typeof params.jsonl === "string" && params.jsonl.trim()
? params.jsonl
: typeof params.jsonlPath === "string" && params.jsonlPath.trim()
? await fs.readFile(params.jsonlPath.trim(), "utf8") // <-- NO PATH VALIDATION
: "";
if (!jsonl.trim()) {
throw new Error(…
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-3689 has been found in openclaw.
Attackers can target a specific entry point like POST /tools/invoke over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.2.21 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-3689" on the vendor's site.
CVE-2026-3689 (openclaw) — CWE-22
Attack surface: POST /tools/invoke / canvas / a2ui_push / jsonlPath
Patched: 2026.2.21 — 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 POST /tools/invoke.
Check the vendor advisory for the affected versions of openclaw. Attack surface: POST /tools/invoke / canvas / a2ui_push / jsonlPath.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.2.21.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /tools/invoke requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /tools/invoke' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /tools/invokeへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade openclaw to 2026.2.21ステージング環境で 2026.2.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /tools/invoke on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com