FlowiseAI Flowise arbitrary file upload vulnerability
CVE-2025-26319 · GHSA-69jq-qr7w-j7qh · published 2025-03-05
- Severity
- High
- CVSS score
- 8.9
- Chance of exploitation (EPSS)
- 55.9%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Total
- CISA SSVC
FlowiseAI Flowise v2.2.6 was discovered to contain an arbitrary file upload vulnerability in /api/v1/attachments.
No fixed release is listed yet for flowise. Limit what it can reach, or stop using it until a fix ships, and follow the source advisory for updates.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 2.2.6 | No fix yet |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- CriticalLangflow: BaseFileComponent-based nodes arbitrary file read with RCE exploitlangflow
- CriticalFlowise NodeVM sandbox escape via puppeteer allowlist - authenticated RCE and arbitrary file read via Chromiumflowise, flowise-components
- CriticalFlowise Prompt Injection to RCE and SSRF via CSV/Airtable Agent Python Validator Bypassflowise, flowise-components
- CriticalCross-IdP account takeover via email-only SSO matchingflowise
- CriticalINVITED users auto-promoted via SSO email match (invite-token bypass)flowise
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.