# CVE-2026-59807: Composio SDK < 0.2.32-beta.283 - Sensitive File Upload via tool-file-uploads.ts

> Attackers can exfiltrate sensitive files like SSH keys by bypassing path validation in the Composio SDK file upload function.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/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:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-jj3x-ph33-pjc6

## What is CVE-2026-59807?

CVE-2026-59807 is a high-severity path traversal vulnerability in ComposioHQ composio, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Composio SDK before 0.2.32-beta.283 contains a path validation bypass vulnerability that allows attackers to read and exfiltrate sensitive files by exploiting a missing assertSafeFileUploadPath check in the readFileFromDisk function within tool-file-uploads.ts. Attackers can exploit prompt injection to manipulate file_uploadable parameters to reference sensitive paths such as SSH private keys, causing the CLI to upload credential files to attacker-controlled storage.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-59807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59807 is a high-severity path traversal vulnerability in ComposioHQ composio, published on 8 Jul 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-59807 exists.

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

## Sources

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

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