Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.5amended

ComposioHQ has a directory traversal vulnerability

CVE-2025-56427GHSA-3mwv-j45g-vp3w

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI composio

    Affected
    <= 0.7.20
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2025-56427: 0.89% estimated exploitation activity in the next 30 days; percentile 59.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-3mwv-j45g-vp3w

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-3mwv-j45g-vp3w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-56427

Advisory: ComposioHQ has a directory traversal vulnerability
IDs: CVE-2025-56427, GHSA-3mwv-j45g-vp3w
Record: https://patchnext.com/advisories/cve-2025-56427 (revision 3, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI composio: affected <= 0.7.20

## Suggested inspection (read-only)
- `python -m pip show composio`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on composio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-3mwv-j45g-vp3w (OSV record GHSA-3mwv-j45g-vp3w lists affected ranges: PyPI composio >=0 <=0.7.20)
- Verified: https://github.com/advisories/GHSA-3mwv-j45g-vp3w (GitHub-reviewed advisory GHSA-3mwv-j45g-vp3w lists affected ranges: PyPI composio >=0 <=0.7.20)

Commands are suggestions: review each one before running it.

Loading voting…