# CVE-2026-7875: NanoClaw Host/Container Filesystem Boundary Vulnerability via Outbound Attachment Handling

> Attackers can read arbitrary host files or delete paths outside the outbox directory via crafted messages or symlinks in NanoClaw.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-42p7-cwm7-4cjg

## What is CVE-2026-7875?

CVE-2026-7875 is a critical path traversal vulnerability in Qwibit NanoClaw, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NanoClaw version 1.2.0 and prior contains a host/container filesystem boundary vulnerability in outbound attachment handling and outbox cleanup that allows a compromised or prompt-injected container to read files outside the intended outbox directory by supplying crafted messages_out.id and content.files values or creating symlinked outbox files. Attackers can exploit this vulnerability to trigger host-side reads of arbitrary files and in some cases achieve recursive deletion of paths outside the intended cleanup target.

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

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

It affects 1 product.


Products: Nanoco Nanoclaw.

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

No fix has been published for CVE-2026-7875 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7875 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7875 is a critical path traversal vulnerability in Qwibit NanoClaw, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7875 exists.

Affected product: Qwibit NanoClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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