# CVE-2025-56427: ComposioHQ has a directory traversal vulnerability

> A remote attacker can exploit a directory traversal flaw in the ComposioHQ library to access sensitive files via the download function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-3mwv-j45g-vp3w, PYSEC-2026-1262

## What is CVE-2025-56427?

CVE-2025-56427 is a high-severity path traversal vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Directory Traversal vulnerability in ComposioHQ v.0.7.20 allows a remote attacker to obtain sensitive information via the _download_file_or_dir function.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-56427?

3 open source packages ship an affected version, including composio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `composio` | PyPI | All versions to 0.7.20 | None |
| `composio` | PyPI | All versions to 0.7.20 | None |
| `composio` | PyPI | All versions to 0.7.20 | None |

Products: Composio Composio.

## How do I fix CVE-2025-56427?

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

## Is CVE-2025-56427 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-8954](https://insights.sbomify.com/CVE-2024-8954/): Authentication Bypass in composiohq/composio (critical 9.8)
- [CVE-2024-8953](https://insights.sbomify.com/CVE-2024-8953/): Unsafe eval usage in composiohq/composio (high 7.2)
- [CVE-2024-8958](https://insights.sbomify.com/CVE-2024-8958/): Unrestricted File Write and Read in composiohq/composio (high 7.2)
- [CVE-2024-8952](https://insights.sbomify.com/CVE-2024-8952/): SSRF in composiohq/composio (medium 6.8)
- [CVE-2024-8955](https://insights.sbomify.com/CVE-2024-8955/): SSRF in composiohq/composio (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-56427 and fix it if it is affected.

What it is: CVE-2025-56427 is a high-severity path traversal vulnerability in n/a, published on 4 Dec 2025. 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-2025-56427 exists.

Affected packages and fixed versions:
- composio (PyPI): affected all versions up to 0.7.20; no fix listed
- composio (PyPI): affected all versions up to 0.7.20; no fix listed
- composio (PyPI): affected all versions up to 0.7.20; no fix listed

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

## Sources

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

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