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


- **Severity:** Medium 6.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-vqvj-w792-h4m6

## What is CVE-2026-127214?

CVE-2026-127214 is a medium-severity vulnerability in FlowiseAI Flowise, published on 13 Nov 2026. 

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-127214?

1 open source package ship an affected version, including flowiseai/flowise.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `flowiseai/flowise` | GitHub | `pkg:github/flowiseai/flowise` | All versions to 3.1.4 | None |

## How do I fix CVE-2026-127214?

No fix has been published for CVE-2026-127214 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-127214 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127214 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127214 and fix it if it is affected.

What it is: CVE-2026-127214 is a medium-severity vulnerability in FlowiseAI Flowise, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-127214 exists.

Affected packages and fixed versions:
- flowiseai/flowise (GitHub): affected all versions up to 3.1.4; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127214/ (Markdown: https://insights.sbomify.com/CVE-2026-127214/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127214
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127214
- OSV: https://osv.dev/vulnerability/CVE-2026-127214

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127214/
Summaries are generated and may contain mistakes; the official description above is the record.
