# CVE-2026-32013: OpenClaw < 2026.2.25 - Symlink Traversal in agents.files Methods

> Attackers can exploit symlink traversal in OpenClaw agent file methods to read or write arbitrary host files, potentially leading to code execution.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 19 Mar 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-fgvx-58p6-gjwc, MINI-qrr2-6976-7xhh

## What is CVE-2026-32013?

CVE-2026-32013 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw versions prior to 2026.2.25 contain a symlink traversal vulnerability in the agents.files.get and agents.files.set methods that allows reading and writing files outside the agent workspace. Attackers can exploit symlinked allowlisted files to access arbitrary host files within gateway process permissions, potentially enabling code execution through file overwrite attacks.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

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.25 |
| `openclaw` | npm | All versions | 2026.2.25 |

Products: Openclaw Openclaw.

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

Upgrade openclaw to 2026.2.25 or later.

## Is CVE-2026-32013 being exploited?

There is no known exploitation of CVE-2026-32013 in the wild and no public exploit code.

Public exploit code:

- OpenClaw CVE scanner. Tracks known vulnerabilities (CVE-2026-32013, CVE-2026-32015, etc.). Zero network calls, 100% local. Version checking, upgrade recommendations. (github_poc): https://github.com/hargabyte/cve-scanner

## 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-32013 and fix it if it is affected.

What it is: CVE-2026-32013 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32013 in the wild and no public exploit code.

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

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-32013/ (Markdown: https://insights.sbomify.com/CVE-2026-32013/index.md)
```

## Sources

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

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