GHSA-g32j-mmxr-gfq5: Flowise RCE via TypeORM DataSource

============================================================================= Security Advisory elttam Topic: Flowise RCE via TypeORM DataSource Module: FlowiseAI/Flowise Disclosed: 15-Apr-2026 Credits: Alex Brown Affects: FlowiseAI/Flowise 3.1.2 I. Background Flowise AI is an open-source, low-code platform for building AI applications—such as chatbots, workflows, and autonomous agents—through an intuitive drag-and-drop interface, minimising the need for extensive coding. Flowise allows users to connect to remote databases within a flow, which is performed using the TypeORM DataSource. II. Problem Description The following nodes allowed users to set arbitrary options for the TypeORM DataSource class using the additionalConfig node input: - packages/components/nodes/recordmanager/MySQLRecordManager/MySQLrecordManager.ts - packages/components/nodes/recordmanager/PostgresRecordManager/PostgresRecordManager.ts - packages/components/nodes/recordmanager/SQLiteRecordManager/SQLiteRecordManager.ts - packages/components/nodes/memory/AgentMemory/MySQLAgentMemory/MySQLAgentMemory.ts - packages/components/nodes/memory/AgentMemory/AgentMemory.ts This is considered a dangerous coding practice, because the options for the TypeORM DataSource class support loading local files as JavaScript code. The following documents the steps to reproduce this RCE vulnerability by abusing the additionalConfig input on a MySQL Record Manager (packages/components/nodes/recordmanager/MySQLRecordManager/MySQLrecordManager.ts) node: 1. Log into a Flowise instance and note the organisation ID in the response from POST /api/v1/auth/login, as shown below. HTTP/1.1 200 OK Set-Cookie: token=<REDACTED>; Path=/; HttpOnly; SameSite=Lax Set-Cookie: refreshToken=<REDACTED>; Path=/; HttpOnly; SameSite=Lax Set-Cookie: connect.sid=<REDACTED>; Path=/; HttpOnly; SameSite=Lax Content-Type: application/json; charset=utf-8 Content-Length: 671 ETag: W/"29f-xnGhZVNYDhOOLUuVSPq0rZLC8mE" Date: Wed, 15 Apr 2026