Read the docs

Server-side request forgery in Flowise Custom Function sandbox

Priority LOW 27CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Flowise through 3.1.4 contains a server-side request forgery flaw in its Custom Function sandbox, where a module subpath inside an allowlisted package evades the SSRF deny list check (CWE-918). An authenticated attacker with chatflows or agentflows create or update permissions can send arbitrary GET and POST requests through POST /api/v1/node-custom-function to loopback, internal network addresses or cloud metadata endpoints. The attacker can map internal networks, disclose credentials and change state on internal services. A public exploit is linked in the references.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

Flowise through 3.1.4 contains a server-side request forgery vulnerability that allows authenticated attackers with chatflows or agentflows create/update permissions to bypass the Custom Function sandbox's SSRF protection by requiring a module subpath inside an allowlisted package, such as axios/dist/node/axios.cjs or node-fetch/lib/index.js, which evades the vm2 mock table and returns an unwrapped HTTP client that skips the checkDenyList validation. Attackers can issue arbitrary GET and POST requests with attacker-controlled bodies via POST /api/v1/node-custom-function to reach loopback and internal-network addresses or the cloud metadata endpoint, enabling network mapping, credential disclosure, and state changes on internal services.

Why it matters now

EPSS 0.00192 8th percentileScored 2026-11-16
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
FlowiseAIFlowiseup to 3.1.4—No fix listedCNA
  • Flowise VendorFlowiseAI Affected up to 3.1.4 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:*——FlowiseAI
  • cpe:2.3:a:flowiseai:flowise:*:*:*:*:*:*:*:* Versions — — ·FlowiseAI

Remediation

The sources list no fixed version for Flowise.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-127214
  2. 2026-11-13 Alias added: GHSA-vqvj-w792-h4m6

References

  • TI-2025-37059 Flowise has Remote Code Execution vulnerability CVSS 3.1CRITICAL 10.0
  • TI-2025-36193 Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover CVSS 3.1CRITICAL 9.8
  • TI-2025-08190 Unsupervised OS command execution leads to remote code execution by unauthenticated network attackers CVSS 3.1CRITICAL 9.8
  • TI-2026-51595 Flowise before 3.1.3 Sandbox Escape via Puppeteer CVSS 4.0CRITICAL 9.4
  • TI-2026-49250 Flowise: CSV Agent Prompt Injection Remote Code Execution Vulnerability CVSS 4.0CRITICAL 9.5
  • TI-2025-43459 Flowise through 2.2.7 - Arbitrary File Write to Remote Code Execution via document-store API CVSS 4.0CRITICAL 10.0
See all 151 →

Sources