Miggo at BlackHat 2026!
Easily map the attack path and prioritize which CVEs are a threat to your organization
Miggo AIGenerate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| flowise | npm | <= 3.1.1 | 3.1.2 |
Miggo AIRoot Cause AnalysisThe vulnerability is a classic mass assignment issue in FlowiseAI's Evaluation and Evaluator endpoints. The root cause is the use of Object.assign(entity, body) without an allowlist of fields, which allows a malicious user to overwrite security-sensitive, server-managed fields like workspaceId and id by simply including them in the request body. This breaks the application's multi-tenant workspace isolation, allowing an authenticated user from one workspace to create or move entities into any other workspace, leading to a full cross-workspace data takeover (IDOR). The patch addresses this by introducing a stripProtectedFields utility function that removes a deny-list of protected fields from the request body before the Object.assign operation is performed. The vulnerable functions are the service methods responsible for creating and updating Evaluation and Evaluator entities, as they were the ones implementing the insecure Object.assign pattern.
createEvaluationpackages/server/src/services/evaluations/index.ts
updateEvaluationpackages/server/src/services/evaluations/index.ts
createEvaluatorpackages/server/src/services/evaluator/index.ts
updateEvaluatorpackages/server/src/services/evaluator/index.ts
EvaluatorDTO.toEntitypackages/server/src/Interface.Evaluation.ts