# CVE-2026-90807: nanocoai NanoClaw Attachment agent-route.ts forwardAttachedFiles link following

> Remote attackers can exploit link following in the attachment handler to read or modify files, requiring a patch for NanoClaw.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-6pc7-x5hm-c6fj

## What is CVE-2026-90807?

CVE-2026-90807 is a medium-severity path traversal vulnerability in nanocoai NanoClaw, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in nanocoai NanoClaw up to 2.1.17. This issue affects the function forwardAttachedFiles of the file src/modules/agent-to-agent/agent-route.ts of the component Attachment Handler. The manipulation results in link following. The attack may be performed from remote. The exploit has been made public and could be used. The patch is identified as 3f9ed607b7e7a4872747295f75286f1c377d7c33. It is advisable to implement a patch to correct this issue.

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

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


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

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

## Is CVE-2026-90807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90807 is a medium-severity path traversal vulnerability in nanocoai NanoClaw, published on 14 Sep 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-90807 exists.

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

## Sources

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

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