CVE-2026-127214
Flowise custom functions could bypass internal-network restrictions
FlowiseAI · Flowise
First documented disclosure · Review checkpoint
Summary
A custom function could obtain an unrestricted HTTP client through an allowed dependency.
Severity and exploitation evidence
Medium · 6.3/10 · CVSS 4.0. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Subpath imports escaped the sandbox’s mocked network client and destination checks.
Conditions required
An authenticated user can create or update chatflows or agentflows.
Potential impact
Requests can reach internal services, expose credentials or change internal service state.
Affected versions and configurations
Through 3.1.4.
Fix and mitigation status
A fixed release remains unverified.
Practical next steps
Restrict custom-function authoring and enforce outbound network controls that deny internal and metadata destinations.
Operating lesson
Apply network policy below user-extensible function environments.
Evidence and limits
Original disclosure 2026-11-10. The CVE Program published this record 2026-11-13. The CNA dates the original public disclosure November 10 and record issuance November 13. Flowise’s public sunset notice increases the importance of verifying ongoing remediation support.
Sources
- VulnCheck CVE authority record
Primary source ·
- Flowise original advisory
Primary source ·
- ENISA EUVD-2026-125728
Primary source ·