Cyber Resilience

CVE-2026-41272

SSRF in Flowiseai Flowise ≤ 3.1.0

Public PoCSSRF
Published
23 April 2026
Modified
24 April 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.0026 17th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2026-41272 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 at the 17th percentile by exploit likelihood (below the median); 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-41272 is a Server-Side Request Forgery (SSRF) vulnerability affecting Flowise, an open-source drag-and-drop user interface for building customized large language model (LLM) flows. In versions prior to 3.1.0, the core security wrappers—secureAxiosRequest and secureFetch—designed to prevent SSRF through allow/deny lists contain multiple logic flaws. These include bypasses via DNS rebinding exploiting a Time-of-Check Time-of-Use (TOCTOU) condition, as well as a default configuration that fails to enforce any deny list. The issue is classified under CWE-918 with 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).

An attacker with low privileges, such as an authenticated user, can exploit this vulnerability over the network with high attack complexity and no user interaction required. Successful exploitation allows high-impact confidentiality and integrity violations—such as unauthorized access to internal network resources or sensitive data—along with low availability impact, potentially enabling actions like reading internal services or modifying data via forged requests.

The official GitHub security advisory (GHSA-2x8m-83vc-6wv4) confirms the vulnerability is fully fixed in Flowise version 3.1.0, recommending immediate upgrades for all prior installations to mitigate the SSRF bypass risks.

Flowise's focus on LLM workflow orchestration introduces AI/ML relevance, as exploited SSRF could potentially target internal AI model endpoints or data pipelines in deployed environments. No public evidence of real-world exploitation has been reported as of the CVE publication on 2026-04-23.

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.1.0, the core security wrappers (secureAxiosRequest and secureFetch) intended to prevent Server-Side Request Forgery (SSRF) contain multiple logic flaws. These flaws allow…

more

attackers to bypass the allow/deny lists via DNS Rebinding (Time-of-Check Time-of-Use) or by exploiting the default configuration which fails to enforce any deny list. This vulnerability is fixed in 3.1.0.

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-31829Same 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.1.0

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