CVE Watchtower

CVE-2026-127214FlowiseAI Flowise Server-Side Request Forgery (SSRF)

NVD

Vulnerability Summary

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.
Severity Level
MEDIUM(6.3)
Published Date
Nov 13, 2026
Last Modified
Nov 13, 2026
Exploitation Status
Public exploit available
EPSS Score (30-Day)
0.19%Probability
Root Weakness (CWE)
The web server receives a URL or similar request from an upstream component and retrieves its contents, but does not sufficiently ensure that the request is being sent to the expected destination.
CVSS v4.0 Base Metrics — Score 6.3 (MEDIUM)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:L/SA:N
Attack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)None
Integrity (Vulnerable System)Low
Availability (Vulnerable System)None
Confidentiality (Subsequent System)High
Integrity (Subsequent System)Low
Availability (Subsequent System)None
Show CVSS v3.x metrics (score 8.5)
CVSS v3.1 Base Metrics — Score 8.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityHigh
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • FlowiseAI Flowise <= 3.1.4
Patched Versions
  • FlowiseAI Flowise 3.1.4

What to do

Prioritize this fix. Exploit code is public, so attacks can follow quickly.

  1. Check whether you run FlowiseAI Flowise and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Review logs and exposed services for signs of earlier compromise.

Timeline

  • Nov 13, 2026Published
  • Nov 13, 2026Record last modified
  • Nov 13, 2026PoC status changed: POC to UNKNOWN

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new FlowiseAI Flowise CVEsYou are reading CVE-2026-127214. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More FlowiseAI Flowise CVEs

Data last checked: Nov 17, 2026 11:11 UTC