Browse / AI Framework and Platform Flaws / CVE-2026-30821
Flowise has Arbitrary File Upload via MIME Spoofing
- Class
- AI Framework and Platform Flaws (filed by a model that read the source)
- Technique
- Cross-site scripting
- Also involves
- Tool and Agent Misuse
- Affected
- flowise (npm)
- Gets past
- Input filter or sanitiser
- CVSS
- CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- EPSS
- 16.7% chance of exploitation in 30 days
How it works, in short
The unauthenticated upload endpoint trusts the client-supplied Content-Type, so attackers can store active files such as scripts by spoofing an allowed type. (Our summary, written by a model. The source text is below.)
Details
Vulnerability Description
---
Vulnerability Overview
- The /api/v1/attachments/:chatflowId/:chatId endpoint is listed in WHITELIST_URLS, allowing unauthenticated access to the file upload API.
- While the server validates uploads based on the MIME types defined in chatbotConfig.fullFileUpload.allowedUploadFileTypes, it implicitly trusts the client-provided Content-Type header (file.mimetype) without verifying the file's actual content (magic bytes) or extension (file.originalname).
- Consequently, an attacker can bypass this restriction by spoofing the Content-Type as a permitted type (e.g., application/pdf) while uploading malicious scripts or arbitrary files. Once uploaded via addArrayFilesToStorage, these files persist in backend storage (S3, GCS, or local disk). This vulnerability serves as a critical entry point that, when chained with other features like static hosting or file retrieval, can lead to Stored XSS, malicious file hosting, or Remote Code Execution (RCE).
Vulnerable Code
- Upload Route Definition
- https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/routes/attachments/index.ts#L7-L10