Flowise before version 3.0.6 has an arbitrary file access vulnerability because the application does not validate that the chatflowId and chatId parameters are UUIDs or numeric identifiers during file operations. Attackers who supply a path‑traversal value for the chatflow ID, such as '../../../../../tmp', can use the /api/v1/chatflows endpoint via addBase64FilesToStorage to write arbitrary files, and read arbitrary files through the /api/v1/get-upload-file and /api/v1/openai-assistants-file/download endpoints via streamStorageFile. The ability to write arbitrary files may allow an unauthenticated attacker to execute code on the host system.

Affected vendors and products include Flowise, with the Flowise application in versions prior to 3.0.6 vulnerable. No other vendors are listed.

The CVSS score for this CVE is 9.3, indicating a critical severity. The EPSS score of 4% indicates a moderate likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The attack vector is inferred to be network‑based through exposed HTTP API endpoints, and the flaw can be exercised without authentication by directly invoking the vulnerable endpoints. Because the application does not validate the path supplied in the chatflow ID, the vulnerability is easily exploitable, especially for attackers who can transmit requests to a public Flowise deployment.