Cyber Resilience

CVE-2026-31829

SSRF in Flowiseai Flowise ≤ 3.0.13

Public PoCSSRF
Published
10 March 2026
Modified
11 March 2026
Patch / advisory
CVSS Score v3.1 7.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS Score 0.023 82th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2026-31829 is a high-severity SSRF (CWE-918) vulnerability in Flowiseai Flowise. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 18% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

This vulnerability is AI-related — categorised as LLM Application Platforms; in the Supply Chain and Deployment risk domain.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-31829 is a Server-Side Request Forgery (SSRF) vulnerability, classified under CWE-918, affecting Flowise versions prior to 3.0.13. Flowise is a drag-and-drop user interface for building customized large language model (LLM) flows. The issue stems from an HTTP Node exposed in AgentFlow and Chatflow components, which performs server-side HTTP requests to user-controlled URLs without restrictions on target hosts. This includes private/internal IP ranges (RFC 1918), localhost, and cloud metadata endpoints, enabling attackers to trick the server into accessing resources not reachable from the public internet. The vulnerability carries a CVSS v3.1 base score of 7.1 (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L).

Any user interacting with a publicly exposed chatflow can exploit this vulnerability by supplying malicious URLs, requiring low privileges (PR:L) but high attack complexity (AC:H) with no user interaction needed beyond normal usage. Successful exploitation allows attackers to force the Flowise server to make unauthorized requests to internal network resources, potentially leading to high confidentiality and integrity impacts (C:H/I:H) such as data exfiltration from internal services, along with low availability impact (A:L).

The official advisory on GitHub (GHSA-fvcw-9w9r-pxc7) confirms the vulnerability is fixed in Flowise version 3.0.13, recommending immediate upgrades to mitigate the SSRF risk. No additional workarounds are specified in the provided details.

Flowise's focus on LLM flows introduces AI/ML relevance, as exploited instances could compromise internal data used in model training or inference pipelines. No real-world exploitation has been reported in the available information.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

AI Security AnalysisAI

AI Category
LLM Application Platforms
Risk Domain
Supply Chain and Deployment
OWASP Top 10 for LLMs 2025
None mapped
Classification Reason
Matched keywords: flowise, large language model

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-41272Same product: Flowiseai Flowise
CVE-2026-41271Same product: Flowiseai Flowise
CVE-2025-59527Same product: Flowiseai Flowise
CVE-2026-43995Same product: Flowiseai Flowise
CVE-2026-56275Same product: Flowiseai Flowise
CVE-2026-41274Same product: Flowiseai Flowise
CVE-2025-29189Same product: Flowiseai Flowise
CVE-2026-41264Same product: Flowiseai Flowise
CVE-2026-41279Same product: Flowiseai Flowise
CVE-2025-61913Same product: Flowiseai Flowise

Affected Assets

flowiseai
flowise
≤ 3.0.13

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
prevents

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
prevents

Network segmentation and egress controls can limit the damage from successful SSRF requests.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Operational threat data describing SSRF campaigns can be used to tighten outbound-request allow-lists and detection rules before attackers exploit them.

References