CVE-2026-30821: Flowise Flowise Has Arbitrary File Upload Vulnerability
HIGHCVE-2026-30821 is a HIGH flowise has arbitrary file upload vulnerability (CWE-434: Unrestricted Upload of File with Dangerous Type) affecting Flowise libraries in the npm ecosystem. The issue involves flowise has arbitrary file upload via mime spoofing. Remediation is available by upgrading affected packages to version 3.0.13.
CVE-2026-30821 at a Glance
How to Fix CVE-2026-30821
To remediate this vulnerability, upgrade all affected Flowise dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install flowise@3.0.13
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls flowise
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-30821, inspect your project dependencies using npm:
npm ls flowise
Analyze the terminal output to locate any version of Flowise in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.13), your application is affected.
Note: The npm ls flowise command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-434: Unrestricted Upload of File with Dangerous Type, where the product allows the upload or transfer of dangerous file types that are automatically processed within its environment. In Flowise, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-30821 Affected Flowise Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
flowise
|
npm |
< 3.0.13
|
3.0.13
|
References
Frequently Asked Questions
What is CVE-2026-30821?
Which Flowise versions are affected?
What version fixes CVE-2026-30821?
Is flowise affected?
What CWE is associated with CVE-2026-30821?
How can I check npm dependencies for CVE-2026-30821?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-j8g8-j7fc-43v6",
"modified" : "2026-03-09T13:15:25Z",
"published" : "2026-03-06T18:49:20Z",
"aliases" : [ "CVE-2026-30821" ],
"summary" : "Flowise has Arbitrary File Upload via MIME Spoofing",
"details" : "### Vulnerability **Description**\n\n---\n\n**Vulnerability Overview**\n \n- The `/api/v1/attachments/:chatflowId/:chatId` endpoint is listed in `WHITELIST_URLS`, allowing unauthenticated access to the file upload API.\n- 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`).\n- 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).\n\n**Vulnerable Code**\n\n- Upload Route Definition\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/routes/attachments/index.ts#L7-L10\n \n ```tsx\n // CREATE\n router.post('/:chatflowId/:chatId', getMulterStorage().array('files'), attachmentsController.createAttachment)\n export default router\n ```\n \n- Mount /api/v1/attachments to the global router\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/routes/index.ts#L72-L77\n \n ```tsx\n const router = express.Router()\n router.use('/ping', pingRouter)\n router.use('/apikey', apikeyRouter)\n router.use('/assistants', assistantsRouter)\n router.use('/attachments', attachmentsRouter)\n ```\n \n- Include /api/v1/attachments in the WHITELIST_URLS list\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/utils/constants.ts#L6-L26\n \n ```tsx\n export const WHITELIST_URLS = [\n '/api/v1/verify/apikey/',\n '/api/v1/chatflows/apikey/',\n '/api/v1/public-chatflows',\n '/api/v1/public-chatbotConfig',\n '/api/v1/public-executions',\n '/api/v1/prediction/',\n '/api/v1/vector/upsert/',\n '/api/v1/node-icon/',\n '/api/v1/components-credentials-icon/',\n '/api/v1/chatflows-streaming',\n '/api/v1/chatflows-uploads',\n '/api/v1/openai-assistants-file/download',\n '/api/v1/feedback',\n '/api/v1/leads',\n '/api/v1/get-upload-file',\n '/api/v1/ip',\n '/api/v1/ping',\n '/api/v1/version',\n '/api/v1/attachments',\n '/api/v1/metrics',\n ```\n \n- Bypass JWT validation if the URL is whitelisted\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/index.ts#L213-L228\n \n ```tsx\n const denylistURLs = process.env.DENYLIST_URLS ? process.env.DENYLIST_URLS.split(',') : []\n const whitelistURLs = WHITELIST_URLS.filter((url) => !denylistURLs.includes(url))\n const URL_CASE_INSENSITIVE_REGEX: RegExp = /\\/api\\/v1\\//i\n const URL_CASE_SENSITIVE_REGEX: RegExp = /\\/api\\/v1\\//\n \n await initializeJwtCookieMiddleware(this.app, this.identityManager)\n \n this.app.use(async (req, res, next) => {\n // Step 1: Check if the req path contains /api/v1 regardless of case\n if (URL_CASE_INSENSITIVE_REGEX.test(req.path)) {\n // Step 2: Check if the req path is casesensitive\n if (URL_CASE_SENSITIVE_REGEX.test(req.path)) {\n // Step 3: Check if the req path is in the whitelist\n const isWhitelisted = whitelistURLs.some((url) => req.path.startsWith(url))\n if (isWhitelisted) {\n next()\n ```\n \n- Multer Configuration: Saves files without file type validation\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/utils/index.ts#L1917-L1960\n \n ```tsx\n export const getUploadPath = (): string => {\n return process.env.BLOB_STORAGE_PATH\n ? path.join(process.env.BLOB_STORAGE_PATH, 'uploads')\n : path.join(getUserHome(), '.flowise', 'uploads')\n }\n \n export function generateId() {\n return uuidv4()\n }\n \n export const getMulterStorage = () => {\n const storageType = process.env.STORAGE_TYPE ? process.env.STORAGE_TYPE : 'local'\n \n if (storageType === 's3') {\n const s3Client = getS3Config().s3Client\n const Bucket = getS3Config().Bucket\n \n const upload = multer({\n storage: multerS3({\n s3: s3Client,\n bucket: Bucket,\n metadata: function (req, file, cb) {\n cb(null, { fieldName: file.fieldname, originalName: file.originalname })\n },\n key: function (req, file, cb) {\n cb(null, `${generateId()}`)\n }\n })\n })\n return upload\n } else if (storageType === 'gcs') {\n return multer({\n storage: new MulterGoogleCloudStorage({\n projectId: process.env.GOOGLE_CLOUD_STORAGE_PROJ_ID,\n bucket: process.env.GOOGLE_CLOUD_STORAGE_BUCKET_NAME,\n keyFilename: process.env.GOOGLE_CLOUD_STORAGE_CREDENTIAL,\n uniformBucketLevelAccess: Boolean(process.env.GOOGLE_CLOUD_UNIFORM_BUCKET_ACCESS) ?? true,\n destination: `uploads/${generateId()}`\n })\n })\n } else {\n return multer({ dest: getUploadPath() })\n }\n }\n ```\n \n- Transfers uploaded files to storage without verification\n \n https://github.com/FlowiseAI/Flowise/blob/d17c4394a238b49327b493c89feee45f3a20bb91/packages/server/src/utils/createAttachment.ts#L124-L158\n \n ```tsx\n const files = (req.files as Express.Multer.File[]) || []\n const fileAttachments = []\n if (files.length) {\n const isBase64 = req.body.base64\n for (const file of files) {\n if (!allowedFileTypes.length) {\n throw new InternalFlowiseError(\n StatusCodes.BAD_REQUEST,\n `File type '${file.mimetype}' is not allowed. Allowed types: ${allowedFileTypes.join(', ')}`\n )\n }\n \n // Validate file type against allowed types\n if (allowedFileTypes.length > 0 && !allowedFileTypes.includes(file.mimetype)) {\n throw new InternalFlowiseError(\n StatusCodes.BAD_REQUEST,\n `File type '${file.mimetype}' is not allowed. Allowed types: ${allowedFileTypes.join(', ')}`\n )\n }\n \n await checkStorage(orgId, subscriptionId, appServer.usageCacheManager)\n \n const fileBuffer = await getFileFromUpload(file.path ?? file.key)\n const fileNames: string[] = []\n // Address file name with special characters: https://github.com/expressjs/multer/issues/1104\n file.originalname = Buffer.from(file.originalname, 'latin1').toString('utf8')\n const { path: storagePath, totalSize } = await addArrayFilesToStorage(\n file.mimetype,\n fileBuffer,\n file.originalname,\n fileNames,\n orgId,\n chatflowid,\n chatId\n )\n ```\n \n\n### PoC\n\n---\n\n**PoC Description**\n \n- Create a local file named `shell.js` containing arbitrary JavaScript code (or a malicious payload).\n- 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).\n- During the upload, retain the filename as `shell.js` but spoof the `Content-Type` header as `application/pdf`.\n- 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.\n\n**PoC**\n\n\n```bash\ncurl -X POST \\\n \"http://localhost:3000/api/v1/attachments/891f64a2-a26f-4169-b333-905dc96c200a/$(uuidgen)\" \\\n -F \"files=@shell.js;type=application/pdf\"\n```\n\n<img width=\"1916\" height=\"1011\" alt=\"image\" src=\"https://github.com/user-attachments/assets/45679d95-00b9-4bee-9c94-7bd9403554d5\" />\n\n\n### Impact\n\n---\n\n**1. Root Cause**\nThe 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.\n\n**2. Key Attack Scenarios**\n\n- **Server Compromise (RCE):** An attacker uploads a **Web Shell** and triggers its execution on the server. Successful exploitation grants system privileges, allowing unauthorized access to internal data and full control over the server.\n- **Client-Side Attack (Stored XSS):** An attacker uploads files containing malicious scripts (e.g., HTML, SVG). When a victim views the file, the script executes within their browser, leading to session cookie theft and account takeover.\n\n**3. Impact**\nThis 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.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "flowise"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.0.13"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.0.12"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-j8g8-j7fc-43v6"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-30821"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/FlowiseAI/Flowise"
}, {
"type" : "WEB",
"url" : "https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.13"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-434" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-06T18:49:20Z",
"nvd_published_at" : "2026-03-07T05:16:26Z"
}
}