criticalCVSS 9.8NVD status: Analyzed

CVE-2026-30821

Flowise is a drag & drop user interface to build a customized large language model flow.

ComponentFlowise
Severitycritical (CVSS 9.8)
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published (NVD)2026-03-07
Last modified2026-06-17
Affected versions
flowise < 3.0.13
Fixed in3.0.13
WeaknessCWE-434
CISA KEVnot listed

NVD description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.0.13, 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). This issue has been patched in version 3.0.13.

Does CVE-2026-30821 hit the version you run?Paste your docker-compose.yml, requirements.txt or package.json. The scanner checks your pinned versions against this CVE and every other one we track for Flowise.
Check my stack

What to do

  • Upgrade Flowise to 3.0.13 or later.
  • Do not expose the component's API or UI to the internet without authentication in front of it.

Sources

Other Flowise CVEs

All Flowise CVEs