Flowise: Authenticated arbitrary file write in the `S3 Directory` document loader via unsanitized S3 object keys
GHSA-88pr-878c-24wf · published 2026-08-04
- Severity
- High
- CVSS score
- 7.2
- Chance of exploitation (EPSS)
- No CVE
- Fixed in
- 3.1.3
Authenticated arbitrary file write to any path writable by the Flowise Destructive overwrite of application data, secrets, or configuration Deployment-dependent lift to RCE if the service account can modify
Upgrade flowise to 3.1.3 or later, and flowise-components to 3.1.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
The repository already has shared path validators that are not used here: packages/components/src/validator.ts:35 defines traversal checks packages/components/src/validator.ts:295 defines sanitizeFileName Recommended fix: 1. Replace path.join(tempDir, key) with a resolve-and-verify flow 2. Reject any resolved path outside tempDir 3. Prefer a sanitized basename if directory structure is not required 4. Apply the same fix to the S3File loader (fileProcessingMethod = unstructured branch)
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| flowise | npm | <= 3.1.2 | 3.1.3 |
| flowise-components | npm | <= 3.1.2 | 3.1.3 |
- 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.