Advisory record · GHSA-6933-jpx5-q87q

Flowise has unsandboxed remote code execution via Custom MCP

CVSS 9.3 CriticalCriticalEPSS 0.011 · 67th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Sept 2025, 20:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flowisenpm>=2.2.7-patch.1, <3.0.63.0.6
Identifiers
GHSA-6933-jpx5-q87q · CVE-2025-71336
Weakness (CWE)
CWE-78 · CWE-862
Published
15 Sept 2025
Updated
3 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Flowise versions from 2.2.7-patch.1 before 3.0.6 are vulnerable to unsandboxed remote code execution through the Custom MCP feature, which runs OS commands such as npx to start local MCP servers. An attacker who can reach a Flowise instance with no authentication configured, or who holds a valid account, can craft a request that runs arbitrary system commands on the host or container. Upgrade to Flowise 3.0.6 or later.

Written 14 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.011, the 67th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 15 Sept 2025, 20:30 UTC Confirmed by GitHub Advisory Database
  2. 3 Nov 2026, 17:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.