CVE-2025-57164VulnerabilityPublished 17 Oct 2025

CVE-2025-57164: Flowise · n/a

Affects FlowiseSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.0.5 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 3.0.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade flowiseai/Flowise to 3.0.5.

Affected software

Product	Affected	Fixed in
GitHubflowiseai/Flowise`pkg:github/flowiseai/Flowise`Other threats	Affected <3.0.5	Fixed in 3.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

These include disabling or restricting access to the 'Supabase RPC Filter' feature if not essential, applying strict input validation and sanitization on all user inputs related to RPC filters, and employing web application firewalls (WAFs) to detect and block suspicious payloads targeting this vector. Network segmentation should be enforced to limit the exposure of Flowise instances to untrusted networks. Monitoring and logging of RPC filter usage should be enhanced to identify anomalous or unauthorized commands. Organizations should also review and harden backend Supabase configurations to minimize the impact of potential command execution. Regular security assessments and penetration testing focused on this vulnerability can help identify exploitation attempts. Finally, staying updated with vendor advisories for patches or updates is critical to apply fixes promptly once available.

Description

CVE-2025-57164 is a medium severity remote code execution vulnerability in Flowise up to version 3.0.4. It arises from unsanitized evaluation of user input in the 'Supabase RPC Filter' field, allowing attackers to execute arbitrary code remotely without authentication or user interaction. The vulnerability is linked to CWE-77, indicating improper neutralization of special elements used in commands. Although no known exploits are currently in the wild, the vulnerability poses a risk to confidentiality and integrity. European organizations using Flowise, especially in sectors relying on Supabase integrations, should prioritize patching or mitigating this flaw. The vulnerability’s network attack vector and lack of required privileges increase its risk profile. Countries with higher adoption of Flowise or Supabase-based solutions, such as Germany, the UK, and the Netherlands, are more likely to be affected. Immediate mitigation includes input validation, restricting RPC filter usage, and monitoring for suspicious activity.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and integrity of data processed through Flowise, especially in environments leveraging Supabase for backend operations. Unauthorized remote code execution could allow attackers to access sensitive customer or operational data, modify application behavior, or disrupt business processes. Sectors such as finance, healthcare, and critical infrastructure that rely on Flowise for data workflows or automation could face regulatory and reputational damage if exploited. The lack of authentication and user interaction requirements increases the likelihood of automated exploitation attempts. Additionally, organizations may face compliance issues under GDPR if personal data is compromised. The medium severity rating suggests that while availability impact is limited, the potential for data leakage and unauthorized system control remains a serious concern. Without timely mitigation, attackers could use this vulnerability as an entry point for broader network compromise within European enterprises.

Summary

CVE-2025-57164 is a remote code execution (RCE) vulnerability affecting Flowise through version 3.0.4. The root cause is the unsanitized evaluation of user-supplied input in the 'Supabase RPC Filter' field, which allows attackers to inject and execute arbitrary commands on the server. This vulnerability is categorized under CWE-77, which involves improper neutralization of special elements used in OS commands or system calls. The vulnerability can be exploited remotely over the network without requiring any privileges or user interaction, making it accessible to unauthenticated attackers. The CVSS v3.1 base score is 6.5, reflecting a medium severity level primarily due to the limited impact on availability and partial impact on confidentiality and integrity. Exploitation could lead to unauthorized disclosure of sensitive data or manipulation of system behavior, potentially compromising the integrity of the affected systems. No patches or official fixes have been released as of the publication date, and no known exploits are currently reported in the wild. The vulnerability specifically targets the Supabase RPC Filter functionality within Flowise, a component that likely interfaces with backend databases or services, increasing the risk of data exposure or backend compromise. Given the nature of the vulnerability, attackers could craft malicious payloads that bypass input validation and execute commands on the host, potentially leading to further lateral movement or data exfiltration.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Oct 2025, 18:21 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats