Flowise Prediction Endpoint Unauthenticated Remote Code Execution – No Vendor Patch Available
Release Date: 10th September 2026
Impact : CRITICAL
TLP Rating: Clear 
The Department of Communications and Digital Transformation (DCDT) through CERT Vanuatu (CERTVU), provides the following advisory.
This alert is relevant to Organizations and developers that operate a self-hosted Flowise instance for building or running visual, low-code AI agent and LLM application workflows. This alert is intended to be understood by technical users and systems administrators.
What is it?
CVE-2026-52098 is a critical, unauthenticated remote code execution vulnerability in Flowise, a widely-adopted open-source, low-code visual builder for AI agents and LLM applications (over 55,000 GitHub stars at the time of writing). A remote attacker can execute arbitrary code via the "/api/v1/prediction/<flowId>" endpoint, without requiring authentication.
What are the systems affected?
The following version(s) are affected:
Flowise (FlowiseAI/Flowise), version 3.1.2 and, given the project's archived status, presumed all subsequent and prior versions relying on the same prediction endpoint – (Affected)
What does this mean?
Step 1 - Endpoint Reached
A remote, unauthenticated attacker sends a specially crafted request to a reachable Flowise instance's "/api/v1/prediction/<flowId>" endpoint.
Step 2 - Arbitrary Code Execution
The crafted request triggers code injection in the prediction-handling logic, allowing the attacker to execute arbitrary code on the server hosting the Flowise instance, without any authentication.
Attack Vectors
A network-based, unauthenticated attack against any Flowise instance with its prediction API reachable from an untrusted network, most critically the public internet.
Indicators of Compromise
Successful exploitation may allow attackers to execute arbitrary code on the server hosting the Flowise instance without any authentication, and to use that code execution to access any credentials, connected data sources, or downstream systems the Flowise instance's AI workflows are configured to use, potentially pivoting into the wider network hosting it.
Mitigation process?
CERTVU recommends the following:
-
Restrict network access to the Flowise instance
Since no vendor patch exists or is expected, restrict access to the Flowise prediction API to trusted internal networks only, and ensure it is never directly reachable from the internet. -
Place the instance behind a Web Application Firewall (WAF)
-
Evaluate migrating to an actively-maintained alternative
-
Monitor for unauthorized activity on the platform
Report any suspected compromise of a Flowise deployment to CERTVU at
Reference
- Download advisory (English): Flowise Prediction Endpoint Unauthenticated Remote Code Execution