CVE-2025-59527VulnerabilityPublished 22 Sep 2025

CVE-2025-59527: FlowiseAI Flowise · Server-Side Request Forgery (SSRF)

Affects FlowiseAI FlowiseSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 3.0.6 : patch FlowiseAI Flowise soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 22 Sep 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-25.

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

Affected software

Product	Affected	Fixed in
FlowiseAI Flowise	Affected =3.0.5	Fixed in–

AI-suggested

European organizations should immediately upgrade Flowise installations from version 3.0.5 to version 3.0.6 or later, where the SSRF vulnerability has been patched. In addition to patching, organizations should implement network segmentation and firewall rules to restrict outbound HTTP requests from application servers to only necessary destinations, reducing the risk of SSRF exploitation. Employing Web Application Firewalls (WAFs) with rules to detect and block SSRF patterns targeting internal IP ranges can provide additional protection. Monitoring and logging outbound requests from Flowise servers can help detect anomalous activity indicative of SSRF exploitation attempts. Organizations should also review and restrict access to the /api/v1/fetch-links endpoint, applying authentication or IP whitelisting where feasible. Regular vulnerability scanning and penetration testing focused on SSRF and related issues should be incorporated into security programs to identify similar risks proactively.

Description

Flowise is a drag & drop user interface to build a customized large language model flow. In version 3.0.5, a Server-Side Request Forgery (SSRF) vulnerability was discovered in the /api/v1/fetch-links endpoint of the Flowise application. This vulnerability allows an attacker to use the Flowise server as a proxy to access internal network web services and explore their link structures. This issue has been patched in version 3.0.6.

Impact

For European organizations using Flowise 3.0.5, this SSRF vulnerability poses a significant risk to internal network confidentiality. Attackers can leverage the Flowise server to bypass perimeter defenses and access internal web services, potentially exposing sensitive data, internal APIs, or administrative interfaces that are not intended for external access. This could facilitate further lateral movement or targeted attacks within the network. Organizations in sectors with high regulatory requirements for data protection, such as finance, healthcare, and critical infrastructure, may face compliance risks if internal data is exposed. Additionally, the ability to map internal link structures can aid attackers in planning more sophisticated attacks. Since the vulnerability does not require authentication or user interaction, it can be exploited remotely and at scale if the vulnerable version is internet-facing. However, the absence of known exploits in the wild suggests limited active exploitation currently, but the risk remains high if unpatched.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (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 22 Sep 2025, 19:53 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats