MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2026-30821

Flowise has Arbitrary File Upload via MIME Spoofing

CVE-2026-30821 ยท 2026-03-06 high

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

PoC

---

PoC Description

- Create a local file named shell.js containing arbitrary JavaScript code (or a malicious payload).
- Send a multipart/form-data request to the /api/v1/attachments/891f64a2-a26f-4169-b333-905dc96c200a/:chatId endpoint without any authentication (login, session, or API keys).
- During the upload, retain the filename as shell.js but spoof the Content-Type header as application/pdf.
- This exploits the server's reliance solely on the client-provided file.mimetype, forcing it to process the malicious JS file as an allowed PDF, thereby confirming unauthenticated arbitrary file upload.

PoC

curl -X POST \
  "http://localhost:3000/api/v1/attachments/891f64a2-a26f-4169-b333-905dc96c200a/$(uuidgen)" \
  -F "files=@shell.js;type=application/pdf"

<img width="1916" height="1011" alt="image" src="https://github.com/user-attachments/assets/45679d95-00b9-4bee-9c94-7bd9403554d5" />

Impact

---

1. Root Cause
The vulnerability stems from relying solely on the MIME type without cross-validating the file extension or actual content. This allows attackers to upload executable files (e.g., .js, .php) or malicious scripts (.html) by masquerading them as benign images or documents.

2. Key Attack Scenarios

3. Impact
This vulnerability is rated as High severity. The risk is particularly critical if the system utilizes shared storage (e.g., S3, GCS) or static hosting features, as the compromise could spread to the entire infrastructure and affect other tenants.

References

Source: GitHub Advisory Database, used under CC BY 4.0.