Security readout for executives and security teams
Plain-English summary
Flowise installations may allow an unauthenticated remote attacker to run operating-system commands through the Custom MCP feature. A successful attack could compromise the Flowise container or host. The issue is rated critical because the described attack path is network reachable, low complexity, and requires no user interaction.
Executive priority
Treat this as urgent for any exposed Flowise deployment. The likely business impact is complete compromise of the application container or server, with potential data theft, service disruption, and lateral movement depending on hosting architecture.
Technical view
CVE-2025-71336 is a CWE-78 command injection/RCE issue in Flowise Custom MCP before 3.0.6. The feature can execute OS commands for local MCP servers, but requests can be crafted to reach the relevant node-load API behavior without adequate sandboxing or access control, leading to arbitrary command execution.
Likely exposure
Highest exposure is Flowise before 3.0.6, especially 2.2.7-patch.1 and earlier, when reachable from untrusted networks. Default installations without FLOWISE_USERNAME and FLOWISE_PASSWORD are especially risky because the source bundle says authentication is absent unless those variables are set.
Exploitation context
The source bundle does not show CISA KEV listing, and no provided source establishes active exploitation. However, the CVSS vector indicates network attackability, low complexity, no privileges, no user interaction, and full confidentiality, integrity, and availability impact.
Researcher notes
Evidence is strongest for affected Flowise versions and the unsandboxed Custom MCP design. The bundle describes minimal authorization, default unauthenticated installs, and a crafted request path. It does not provide KEV confirmation or independent proof of exploitation in the supplied materials.
Mitigation direction
- Upgrade Flowise to 3.0.6 or later using vendor guidance.
- Set FLOWISE_USERNAME and FLOWISE_PASSWORD where Flowise remains deployed.
- Restrict Flowise access to trusted networks or authenticated gateways.
- Disable or tightly control Custom MCP until upgraded and verified.
- Review vendor and VulnCheck advisories for any updated hardening guidance.
Validation and detection
- Inventory all Flowise deployments and record installed versions.
- Confirm whether affected instances are reachable from the internet or partner networks.
- Check whether Flowise authentication environment variables are configured.
- Review logs for suspicious Custom MCP or node-load API activity.
- Verify upgraded instances report Flowise 3.0.6 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-71336 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: 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
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-6933-jpx5-q87q)CVE reference, VulnCheck · vendor-advisory
- VulnCheck Advisory: Flowise - Unsandboxed Remote Code Execution via Custom MCPCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.