Skip to content
Applications

CVE-2026-59807

8.9
High
EPSS 0.47%Patch availableJul 9, 2026

Path validation bypass in Composio SDK CLI allows local file exfiltration.

common questions

Is CVE-2026-59807 being exploited?

Not confirmed. CVE-2026-59807 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.47% probability of exploitation in the next 30 days.

How severe is CVE-2026-59807?

CVE-2026-59807 is rated High with a CVSS score of 8.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59807?

Yes. A fix has been recorded for CVE-2026-59807. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59807 affect?

CVE-2026-59807 affects Composio SDK < 0.2.32-beta.283, Composio CLI (tool-file-uploads.ts), readFileFromDisk function, Developer workstations running the Composio CLI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59807?

Upgrade to >=0.2.32-beta.283; rotate exposed credentials; restrict/untrusted CLI prompts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Composio SDK < 0.2.32-beta.283Composio CLI (tool-file-uploads.ts)readFileFromDisk functionDeveloper workstations running the Composio CLI
impact

Prompt-injection enables reading and uploading local sensitive files (e.g., SSH keys) to attacker-controlled storage.

action required

Immediate action required

affected versions
ComposioHQ composio
  • affected< 0.2.32-beta.283

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free