Flowise has unsandboxed remote code execution via Custom MCP

Flowise

The Custom MCPs feature is designed to execute OS commands, for instance, using tools like npx to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC).

First seen: 15 Sept 2025
Last update: 15 Sept 2025, 20:30 UTC
Versions per GitHub advisory, not the vendor: flowise 3.0.6
Identifiers: CVE-2025-71336
CVSS: 9.8
Source: GitHub advisory
On the menu as: LLM gateways
npm packages

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Flowise has unsandboxed remote code execution via Custom MCP
Severity: critical. Patch status: fix status unknown.
Affected: Flowise
Versions per GitHub advisory, not the vendor: flowise 3.0.6
Ids: CVE-2025-71336

The Custom MCPs feature is designed to execute OS commands, for instance, using tools like npx to spin up local MCP Servers. However, Flowise's inherent authentication and authorization model is minimal and lacks role-based access controls (RBAC).

## Steps
1. Search every lockfile and manifest (package-lock.json, yarn.lock, pnpm-lock.yaml, requirements*.txt, poetry.lock, uv.lock, composer.lock, go.sum, Cargo.lock, Gemfile.lock) for `flowise`. For each hit, compare the installed version with the version on the same major line (per GitHub advisory, not the vendor, so check the vendor's advisory before treating it as a fix): flowise 3.0.6. If it's lower, give the exact upgrade command for the package manager this repo uses.
2. This incident involves a provider (ai-gateways). Search config, CI and env templates (.env.example, wrangler.toml, vercel.json, terraform, workflow secrets) for credentials stored there. List each secret by name, where it is used, and how to rotate it. Never print secret values.
3. Versions per GitHub advisory, not the vendor: flowise: >= 2.2.7-patch.1 < 3.0.6 → 3.0.6. Flowise: 3.0.6. Don't treat them as a fix until the vendor says so.

## Fix by release line
| Line | State | Fix | Until then |
|---|---|---|---|
| flowise >= 2.2.7-patch.1 < 3.0.6 | per GitHub advisory, not the vendor | 3.0.6 | restrict network access to it |
| Flowise | per the CVE record from VulnCheck, not the vendor | 3.0.6 | restrict network access to it |

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2025-71336") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://github.com/FlowiseAI/Flowise/commit/ac7cf30e019cde54905bf09b5d3fe1c6ba42f9b9 https://github.com/FlowiseAI/Flowise/pull/5201 https://github.com/FlowiseAI/Flowise/releases/tag/flowise%403.0.6 https://github.com/FlowiseAI/Flowise/security/advisories/GHSA-6933-jpx5-q87q https://github.com/advisories/GHSA-6933-jpx5-q87q
https://pwned.coffee/i/flowise-has-unsandboxed-remote-code-execution-via-custom-cve-2025-71336

Receipt

Exploitation: Public exploit code, no attacks reported
CISA ADP “CISA ADP rates exploitation of CVE-2025-71336 "poc" (SSVC).” source
By release line, per GitHub advisory, not the vendor: Product Affected Version named Source
flowise (npm) >= 2.2.7-patch.1, < 3.0.6 3.0.6 GitHub advisory per GitHub advisory, not the vendor checked 3 Nov
Flowise before 3.0.6 3.0.6 CVE record (CNA) per the CVE record from VulnCheck, not the vendor checked 3 Nov
Score: CVSS 9.8 (critical). CVSS 3.1 9.8 (CNA VulnCheck) for CVE-2025-71336
Last checked: 3 Nov 2026, 20:33 UTC

Product	Affected	Version named	Source
flowise (npm)	>= 2.2.7-patch.1, < 3.0.6	3.0.6	GitHub advisory per GitHub advisory, not the vendor checked 3 Nov
Flowise	before 3.0.6	3.0.6	CVE record (CNA) per the CVE record from VulnCheck, not the vendor checked 3 Nov

Sources: KEV – CVE record ✓ Vendor –

Sources

Totalone very hot coffee