Critical

Flowise Pre-auth Arbitrary File Upload

  • Disclosed: 13.03.2025
  • Updated: 11.10.2026 10:22

Summary

An unauthorized attacker can leverage the whitelisted route /api/v1/attachments to upload arbitrary files when the storageType is set to local (default).

Details

When a new request arrives, the system first checks if the URL starts with /api/v1/. If it does, the system then verifies whether the URL is included in the whitelist (whitelistURLs). If the URL is whitelisted, the request proceeds; otherwise, the system enforces authentication.

@ /packages/server/src/index.ts

ts
           this.app.use(async (req, res, next) => {
                // Step 1: Check if the req path contains /api/v1 regardless of case
                if (URL_CASE_INSENSITIVE_REGEX.test(req.path)) {
                    // Step 2: Check if the req path is case sensitive
                    if (URL_CASE_SENSITIVE_REGEX.test(req.path)) {
                        // Step 3: Check if the req path is in the whitelist
                        const isWhitelisted = whitelistURLs.some((url) => req.path.startsWith(url))
                        if (isWhitelisted) {
                            next()
                        } else if (req.headers['x-request-from'] === 'internal') {
                            basicAuthMiddleware(req, res, next)
                        } else {
                            const isKeyValidated = await validateAPIKey(req)
                            if (!isKeyValidated) {
                                return res.status(401).json({ error: 'Unauthorized Access' })
                            }
                            next()
                        }
                    } else {
                        return res.status(401).json({ error: 'Unauthorized Access' })
                    }
                } else {
                    // If the req path does not contain /api/v1, then allow the request to pass through, example: /assets, /canvas
                    next()
                }
            }

The whitelist is defined as follows

ts
export const WHITELIST_URLS = [
    '/api/v1/verify/apikey/',
    '/api/v1/chatflows/apikey/',
    '/api/v1/public-chatflows',
    '/api/v1/public-chatbotConfig',
    '/api/v1/prediction/',
    '/api/v1/vector/upsert/',
    '/api/v1/node-icon/',
    '/api/v1/components-credentials-icon/',
    '/api/v1/chatflows-streaming',
    '/api/v1/chatflows-uploads',
    '/api/v1/openai-assistants-file/download',
    '/api/v1/feedback',
    '/api/v1/leads',
    '/api/v1/get-upload-file',
    '/api/v1/ip',
    '/api/v1/ping',
    '/api/v1/version',
    '/api/v1/attachments',
    '/api/v1/metrics'
]

This means that every route in the whitelist does not require authentication. Now, let's examine the /api/v1/attachments route.

@ /packages/server/src/routes/attachments/index.ts

ts
const router = express.Router()
// CREATE
router.post('/:chatflowId/:chatId', getMulterStorage().array('files'), attachmentsController.createAttachment)
export default router

After several calls, the request reaches the createFileAttachment function @ (packages/server/src/utils/createAttachment.ts) Initially, the function retrieves chatflowid and chatId from the request without any additional validation. The only check performed is whether these parameters exist in the request.

ts
    const chatflowid = req.params.chatflowId
    if (!chatflowid) {
        throw new Error(
            'Params chatflowId is required! Please provide chatflowId and chatId in the URL: /api/v1/attachments/:chatflowId/:chatId'
        )
    }

    const chatId = req.params.chatId
    if (!chatId) {
        throw new Error(
            'Params chatId is required! Please provide chatflowId and chatId in the URL: /api/v1/attachments/:chatflowId/:chatId'
        )
    }

Next, the function retrieves the uploaded files and attempts to add them to the storage by calling the addArrayFilesToStorage function.

ts
const files = (req.files as Express.Multer.File[]) || []
    const fileAttachments = []
    if (files.length) {
        // ...
        for (const file of files) {
            const fileBuffer = await getFileFromUpload(file.path ?? file.key)  // get the uploaded file
            const fileNames: string[] = []
            file.originalname = Buffer.from(file.originalname, 'latin1').toString('utf8')
            // add it to the storage
            const storagePath = await addArrayFilesToStorage(file.mimetype, 
                                                             fileBuffer,
                                                             file.originalname,
                                                             fileNames,
                                                             chatflowid, chatId) // add it to the storage

            // ...

            await removeSpecificFileFromUpload(file.path ?? file.key) // delete from tmp
           //  ...

                fileAttachments.push({
                    name: file.originalname,
                    mimeType: file.mimetype,
                    size: file.size,
                    content
                })
            } catch (error) {
                throw new Error(`Failed operation: createFileAttachment - ${getErrorMessage(error)}`)
            }
        }
    }

    return fileAttachments

Now lets take a look at addArrayFilesToStorage function @ (/packages/components/src/storageUtils.ts)

ts
export const addArrayFilesToStorage = async (mime: string, bf: Buffer, fileName: string, fileNames: string[], ...paths: string[]) => {
    const storageType = getStorageType()

    const sanitizedFilename = _sanitizeFilename(fileName)
    if (storageType === 's3') {
      // ...
    } else {
        const dir = path.join(getStoragePath(), ...paths) // PATH TRAVERSAL.
        if (!fs.existsSync(dir)) {
            fs.mkdirSync(dir, { recursive: true })
        }
        const filePath = path.join(dir, sanitizedFilename)
        fs.writeFileSync(filePath, bf)
        fileNames.push(sanitizedFilename)
        return 'FILE-STORAGE::' + JSON.stringify(fileNames)
    }
}

As noted in the comment, to construct the directory, the function joins the output of the getStoragePath function with ...paths, which are essentially the chatflowid and chatId extracted earlier from the request. However, as mentioned previously, these values are not validated to ensure they are UUIDs or numbers. As a result, an attacker could manipulate these variables to set the dir variable to any value. Combined with the fact that the filename is also provided by the user, this leads to unauthenticated arbitrary file upload.

POC

This is the a HTTP request. As observed, we are not authenticated, and by manipulating the chatId parameter, we can perform a path traversal. In this example, we overwrite the api.json file, which contains the API keys for the system.

File Uplaod Vulnerability.

in this example, the dir variable will be

ts
var dir = '/root/.flowise/storage/test/../../../../../../../../root/.flowise/'

and the file name is api.json

And the API Keys in the UI

File Uplaod Vulnerability.

Impact

This vulnerability could potentially lead to

  • Remote Code Execution
  • Server Takeover
  • Data Theft And more

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package flowise <= 2.2.7 no fix

References

CVSS score -
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-434
Platform
npm
Package
flowise
Disclosed
13.03.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-h42x-xx2q-6v6g - CC BY 4.0

Vulnerability history: flowise

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (114) in the archive
Total entries
114
First → latest
04.2024 10.2026
Without a fix
16
Exploited in attacks
0

Severity breakdown

  • Critical 28
  • High 62
  • Medium 24

Disclosures per year

  1. 2024: 11
  2. 2025: 22
  3. 2026: 81
Severity:
  1. Critical CVE-2026-69259 < 3.1.3 3.1.3
  2. Critical CVE-2026-69256 < 3.1.3 3.1.3
  3. Critical CVE-2026-69253 < 3.1.3 3.1.3
  4. Critical CVE-2026-69251 < 3.1.3 3.1.3
  5. High · 8.8 CVE-2026-46444 < 3.1.2 3.1.2
  6. High CVE-2026-46443 < 3.1.2 3.1.2
  7. High CVE-2026-56274 < 3.1.2 3.1.2
  8. High · 7.5 CVE-2026-46440 < 3.1.2 3.1.2
  9. High · 9.8 CVE-2026-41276 < 3.1.0 3.1.0
  10. High CVE-2026-41274 < 3.1.0 3.1.0
  11. High · 7.5 CVE-2026-41275 < 3.1.0 3.1.0
  12. High · 7.1 CVE-2026-41271 < 3.1.0 3.1.0
  13. High · 7.1 CVE-2026-41272 < 3.1.0 3.1.0
  14. High · 7.1 CVE-2026-41269 < 3.1.0 3.1.0
  15. High · 7.7 CVE-2026-41268 < 3.1.0 3.1.0
  16. High · 7.5 CVE-2026-41266 < 3.1.0 3.1.0
  17. Critical · 8.8 CVE-2026-41137 < 3.1.0 3.1.0
  18. Critical · 9.9 CVE-2026-40933 < 3.1.0 3.1.0
  19. High CVE-2026-30824 < 3.0.13 3.0.13
  20. High · 7.7 CVE-2026-30822 < 3.0.13 3.0.13
  21. High CVE-2026-30821 < 3.0.13 3.0.13
  22. Critical · 9.9 CVE-2025-61913 < 3.0.8, < 3.0.8 3.0.8
  23. High · 8.3 CVE-2025-61687 >= 3.0.7, < 3.0.8 3.0.8
  24. Critical · 9.8 CVE-2025-55346 <= 2.2.7-patch.1 no fix
  25. High CVE-2025-71336 >= 2.2.7-patch.1, < 3.0.6 3.0.6
  26. Critical · 9.8 CVE-2025-71334 >= 2.2.8, < 3.0.6 3.0.6
  27. Critical · 9.1 CVE-2025-71324 >= 3.0.5, < 3.0.6 3.0.6
  28. Critical · 10.0 CVE-2025-59528 >= 3.0.5, < 3.0.6 3.0.6
  29. High · 7.5 CVE-2025-59527 >= 3.0.5, < 3.0.6 3.0.6
  30. Critical · 9.1 CVE-2025-57164 >= 3.0.5, < 3.0.6 3.0.6
  31. Critical · 9.8 CVE-2025-8943 <= 3.0.5 no fix
  32. Critical · 10.0 CVE-2025-71338 <= 2.2.7 no fix
  33. Flowise Pre-auth Arbitrary File Upload this entry
    Critical CVE-2025-71333 <= 2.2.7 no fix
  34. High CVE-2025-26319 <= 2.2.6 no fix
  35. High CVE-2024-58351 < 2.1.4 2.1.4
  36. High · 7.5 CVE-2024-8182 <= 1.8.2 no fix
  37. High · 7.3 CVE-2024-8181 <= 1.8.2 no fix
  38. High · 7.5 CVE-2024-36421 <= 1.4.3 no fix
  39. High · 7.5 CVE-2024-36420 <= 1.4.3 no fix
  40. High · 7.6 CVE-2024-31621 < 1.8.1 1.8.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.