# CVE-2026-3689: OpenClaw Canvas Path Traversal Information Disclosure Vulnerability

> Authenticated attackers can exploit path traversal in the canvas gateway to disclose sensitive information via file operations.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-jq4x-98m3-ggq6, GHSA-xq39-5c6m-mcq7, MINI-98w9-cfmx-jw54, MINI-gr9m-vpj7-24j7

## What is CVE-2026-3689?

CVE-2026-3689 is a medium-severity path traversal vulnerability in Openclaw Openclaw, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-3689?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.2.21 |
| `openclaw` | npm | All versions | 2026.2.21 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-3689?

Upgrade openclaw to 2026.2.21 or later.

## Is CVE-2026-3689 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3689 exists.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3689 and fix it if it is affected.

What it is: CVE-2026-3689 is a medium-severity path traversal vulnerability in Openclaw Openclaw, published on 11 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3689 exists.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.21
- openclaw (npm): affected all versions; fixed in 2026.2.21

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3689/ (Markdown: https://insights.sbomify.com/CVE-2026-3689/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3689
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3689
- OSV: https://osv.dev/vulnerability/CVE-2026-3689

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3689/
Summaries are generated and may contain mistakes; the official description above is the record.