How severe is CVE-2024-8865?

No CVSS score has been assigned to CVE-2024-8865 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-8865?

CVE-2024-8865 affects the following packages: composio-core (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-8865?

The records we use list no patched version of composio-core for CVE-2024-8865. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2024-8865 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for composio-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-8865 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2024-8865 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2024-8865, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-8865?

CVE-2024-8865 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-8865?

CVE-2024-8865 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-8865 published, and has it been updated?

CVE-2024-8865 was published on September 15, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2024-8865 — composio-core

CVE-2024-8865 is a Path Traversal vulnerability in composio-core. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

composiohq composio api.py path path traversal

Also known asGHSA-66r2-xm28-74w9PYSEC-2026-1265

Published

Sep 15, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-8865.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍composio-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in composiohq composio up to 0.5.8 and classified as problematic. Affected by this issue is the function path of the file composio\server\api.py. The manipulation of the argument file leads to path traversal. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`composio-core`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

composiocomposio

≤ 0.5.8

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A vulnerability was found in composiohq composio up to 0.5.8 and classif…

rumbling-slice-eb0.notion.siteNVDSep 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for composio-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of composio-core for CVE-2024-8865. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-8865 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works