cve.bz

CVE-2026-127214 Flowise 3.1.4 SSRF Bypass via Custom Function Sandbox

6.3 medium

Medium (6.3) in flowiseai flowise.

On this page
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

CVSS 4.0

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

CVSS 3.1

8.5 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-127214 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-127214?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-127214?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-127214 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-127214

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-127214](https://cve.bz/cve/badge/CVE-2026-127214.svg)](https://cve.bz/cve/CVE-2026-127214)

HTML:

<a href="https://cve.bz/cve/CVE-2026-127214"><img src="https://cve.bz/cve/badge/CVE-2026-127214.svg" alt="CVE-2026-127214"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
FlowiseAI Flowisethrough 3.1.4

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON