dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-41268

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 3.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 is a drag & drop user interface to build a customized large language model flow. Prior to 3.1.0, Flowise is vulnerable to a critical unauthenticated remote command execution (RCE) vulnerability. It can be exploited via a parameter override bypass using the FILE-STORAGE:: keyword combined with a NODE_OPTIONS environment variable injection. This allows for the execution of arbitrary system commands with root privileges within the containerized Flowise instance, requiring only a single HTTP request and no authentication or knowledge of the instance. This vulnerability is fixed in 3.1.0.

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 prior to 3.1.0 contain an unauthenticated remote command execution vulnerability exploited via a parameter override bypass using the FILE-STORAGE:: keyword combined with NODE_OPTIONS environment variable injection, allowing arbitrary system command execution with root privileges in containerized environments through a single HTTP request.

MitigationUpgrade to Flowise version 3.1.0 or later to remediate this vulnerability.

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.1.0

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. Determine installed Flowise version
    Check the package.json file in the Flowise installation directory, or query the running service's version endpoint if available, or run 'npm list flowise' from the installation directory
    Affected if The version number is lower than 3.1.0 (e.g., 3.0.x, 2.x.x, etc.)
  2. Identify if FILE-STORAGE module is configured
    Review the Flowise configuration files for any storage provider settings that use the FILE-STORAGE:: prefix, or check environment variables for storage-related configuration
    Affected if FILE-STORAGE or any storage provider is explicitly configured in the configuration files or environment variables
  3. Inspect NODE_OPTIONS environment variable
    Run 'echo $NODE_OPTIONS' on the server running Flowise, or check the systemd service file or startup scripts for NODE_OPTIONS assignment
    Affected if NODE_OPTIONS is set to any value (particularly if it can be controlled by an attacker or is used in the Flowise process startup)
  4. Verify network exposure of Flowise service
    Check if the Flowise HTTP port (typically 3000 or 8080) is exposed to untrusted networks, or review firewall rules and reverse proxy configurations
    Affected if The Flowise service is accessible from the internet or untrusted networks without authentication protection

You are affected if Flowise version is below 3.1.0 AND the FILE-STORAGE feature is enabled in your configuration, as the vulnerability combines these elements with NODE_OPTIONS injection for pre-auth RCE.

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.1.0 or later
Fixed in 3.1.0
Interim mitigation

Upgrade to Flowise version 3.1.0 or later to remediate this vulnerability.

Recommended fix High confidence

Flowise 3.1.0 or later

  1. 1. Back up your current Flowise installation, including all configuration files and data directories
  2. 2. Stop the running Flowise service
  3. 3. Upgrade Flowise to version 3.1.0 or later by following the official installation method for your deployment (npm, Docker, or binary)
  4. 4. Start the upgraded Flowise service
  5. 5. Verify the application is running correctly and the vulnerability is no longer present

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

Fix this in Flowise Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41268 — 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-2026-41268 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