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.
CVE-2026-59807
Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. a secondary CVSS source baseline 6.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(high)
- EPSS
- 20.8%
- KEV
- Not listed
Published
July 8, 2026
Last Modified
July 10, 2026
Advisory Details (4)
Auto-updated Jul 8, 2026Composio SDK < 0.2.32-beta.283 - Sensitive File Upload via tool-file-uploads.ts | Advisories | VulnCheck
https://www.vulncheck.com/advisories/composio-sdk-beta-283-sensitive-file-upload-via-tool-file-uploads-tsfix(cli): enforce sensitive-file upload denylist (GHSA-hp3h-89pf-5q58)
Patch available: ComposioHQ/composio @composio/[email protected] (PR #3763 merged 2026-07-06)
https://github.com/ComposioHQ/composio/pull/3763Composio CLI tool-file-uploads path bypasses sensitive-file denylist, enabling credential exfiltration in agentic workflows · Issue #3746 · ComposioHQ/composio · GitHub
https://github.com/ComposioHQ/composio/issues/3746commit fc17c37bf95b (ComposioHQ/composio)
Patch available: ComposioHQ/composio @composio/[email protected] (contains commit fc17c37bf95b)
https://github.com/ComposioHQ/composio/commit/fc17c37bf95b7ece5c038cb7e2ab7e3e4a064e3aVendor Advisories for CVE-2026-59807(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 20:44 UTCEG score recompute
- 2026-07-11 20:44 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 20:35 UTCEG score recompute
- 2026-07-10 20:34 UTCGHSA enrichment
- 2026-07-09 20:25 UTCEG score recompute
- 2026-07-09 20:25 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 20:16 UTCEG score recompute
- 2026-07-08 20:14 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-59807?
When was CVE-2026-59807 disclosed?
Is CVE-2026-59807 actively exploited?
What is the CVSS score of CVE-2026-59807?
How do I remediate CVE-2026-59807?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-59807
Is Your Infrastructure Affected by CVE-2026-59807?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.