Skip to main content
VulnerabilityPublished

CVE-2026-31829: FlowiseAI Flowise · Server-Side Request Forgery (SSRF)

Affects FlowiseAI FlowiseSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 3.0.13 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
2.4% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.13
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade Flowise and flowiseai/Flowise to 3.0.13.

Affected software

ProductAffectedFixed in
FlowiseAIFlowiseAffected
  • <3.0.13
Fixed in
  • 3.0.13
GitHubflowiseai/Flowisepkg:github/flowiseai/FlowiseOther threatsAffected
  • <3.0.13
Fixed in
  • 3.0.13

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

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade Flowise to version 3.0.13 or later, where the SSRF issue is fixed. If upgrading is not immediately possible, implement strict network-level controls such as firewall rules or egress filtering to prevent the Flowise server from making HTTP requests to internal IP ranges (RFC 1918), localhost (127.0.0.1), and cloud metadata service IP addresses (e.g., 169.254.169.254). Additionally, apply application-layer input validation to restrict or sanitize user-supplied URLs in the HTTP Node to allow only trusted external domains. Monitoring and logging HTTP requests originating from the Flowise server can help detect suspicious activity. Employ network segmentation to isolate the Flowise server from sensitive internal resources. Finally, review and harden access controls on internal services to minimize the impact of potential SSRF exploitation.

Description

Flowise is a drag & drop user interface to build a customized large language model flow. Prior to 3.0.13, Flowise exposes an HTTP Node in AgentFlow and Chatflow that performs server-side HTTP requests using user-controlled URLs. By default, there are no restrictions on target hosts, including private/internal IP ranges (RFC 1918), localhost, or cloud metadata endpoints. This enables Server-Side Request Forgery (SSRF), allowing any user interacting with a publicly exposed chatflow to force the Flowise server to make requests to internal network resources that are inaccessible from the public internet. This vulnerability is fixed in 3.0.13.

References

Community reviews

Loading reviews…