dbcve.org
FlowiseApplication · Flowiseai

CVE-2025-71336

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-25
Fix available
A fix is available. Upgrade to 3.0.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Flowise before 3.0.6 (affected versions 2.2.7-patch.1 and earlier) contains an unsandboxed remote code execution vulnerability in the Custom MCP feature, which is designed to execute OS commands such as launching local MCP servers. Because Flowise's authentication and authorization model is minimal and lacks role-based access control, and the default installation runs without authentication unless FLOWISE_USERNAME and FLOWISE_PASSWORD are set, an attacker can send a crafted JSON payload with the header 'x-request-from: internal' to the /api/v1/node-load-method/customMCP endpoint to execute arbitrary OS commands, resulting in complete compromise of the platform container or server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Flowise versions before 3.0.6 contain an unsandboxed remote code execution vulnerability in the Custom MCP feature. Attackers can send crafted JSON payloads to /api/v1/node-load-method/customMCP with the header 'x-request-from: internal' to execute arbitrary OS commands without authentication, resulting in complete compromise of the container or server.

MitigationEnable authentication by setting FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables immediately, upgrade to version 3.0.6 or later, and implement network segmentation to restrict access to the API endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FlowiseApplication
Affected:< 3.0.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Flowise installation and version
    Locate the Flowise application (check running processes, Docker containers, or installation directory). Run 'flowise version' or check package.json, Docker image tag, or the /api/v1/version endpoint to determine the installed version.
    Affected if Installed version is before 3.0.6 (e.g., 3.0.5, 3.0.4, earlier versions)
  2. Verify if authentication is enabled
    Check if FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables are set on the Flowise server. Run 'env | grep FLOWISE' or inspect the Docker container/environment configuration.
    Affected if Either FLOWISE_USERNAME or FLOWISE_PASSWORD environment variable is missing or unset - authentication is disabled and the vulnerability is exploitable
  3. Confirm network exposure to the API endpoint
    Determine if the Flowise API (port typically 3000) is accessible from untrusted networks. Check firewall rules, reverse proxy configuration, and container network settings.
    Affected if The /api/v1/node-load-method/customMCP endpoint is reachable from outside trusted networks without additional access controls
  4. Check for suspicious access patterns
    Review server, container, or proxy logs for POST requests to /api/v1/node-load-method/customMCP with the 'x-request-from: internal' header, especially from unexpected sources.
    Affected if Such requests are found in logs, indicating potential exploitation attempts

You are affected if Flowise version is below 3.0.6 AND authentication (FLOWISE_USERNAME/FLOWISE_PASSWORD) is not enabled, making the unsandboxed Custom MCP endpoint directly exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.0.6 or later
Fixed in 3.0.6
Interim mitigation

Enable authentication by setting FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables immediately, upgrade to version 3.0.6 or later, and implement network segmentation to restrict access to the API endpoint.

Recommended fix High confidence

Flowise 3.0.6 or later

  1. Upgrade Flowise to version 3.0.6 or later to obtain the patched release
  2. If using Docker, update the image tag to the fixed version (e.g., flowiseai/flowise:3.0.6 or later) and redeploy the container
  3. If using npm/pnpm, run 'npm install [email protected]' or 'pnpm install [email protected]' to update the package
  4. Restart the Flowise service after upgrading
  5. Verify the upgrade was successful by checking the Flowise version in the UI or via API
  6. (Recommended) Set FLOWISE_USERNAME and FLOWISE_PASSWORD environment variables to enable authentication if not already configured

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Flowise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-71336 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-71336 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data