# CVE-2026-32846: OpenClaw < 2026.3.28 Media Parsing Path Traversal to Arbitrary File Read

> Attackers can read arbitrary files, including system files and SSH keys, by exploiting path traversal flaws in OpenClaw's media parsing logic.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-f6pf-4gjx-c94r, GHSA-hggm-x7r9-mm7v, MINI-9r23-69ff-vj3v, MINI-p49q-j29p-x42j

## What is CVE-2026-32846?

CVE-2026-32846 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw before 2026.3.28 contains a path traversal vulnerability in media parsing that allows attackers to read arbitrary files by bypassing path validation in the isLikelyLocalPath() and isValidMedia() functions. Attackers can exploit incomplete validation and the allowBareFilename bypass to reference files outside the intended application sandbox, resulting in disclosure of sensitive information including system files, environment files, and SSH keys.

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

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

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


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

Products: Openclaw Openclaw.

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

Upgrade openclaw to a fixed version for your release line: 2026.03.28 or 2026.3.28.

## Is CVE-2026-32846 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32846 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-32846 and fix it if it is affected.

What it is: CVE-2026-32846 is a high-severity path traversal vulnerability in Openclaw Openclaw, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32846 exists.

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

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

## Sources

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

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