dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-46442

CRITICAL · 9.9 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 3.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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 version 3.1.2, POST /api/v1/node-custom-function lacks route-level authorization, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured — the common deployment case — Flowise executes this code inside a NodeVM sandbox. This sandbox can be escaped, allowing an attacker to reach the host process object and execute system commands via child_process. The result is authenticated remote code execution on the Flowise server host. This issue has been patched in version 3.1.2.

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.1.2 have a missing route-level authorization vulnerability on POST /api/v1/node-custom-function, allowing any authenticated user or API key to submit arbitrary JavaScript to the Custom JS Function node. When E2B_APIKEY is not configured (the common deployment case), Flowise executes this code in a NodeVM sandbox that can be escaped to access the host process object and execute system commands via child_process, resulting in authenticated remote code execution.

MitigationUpgrade to Flowise version 3.1.2 or later. If upgrading is not immediately possible, ensure E2B_APIKEY is properly configured to avoid using the vulnerable NodeVM sandbox, and implement additional authentication controls on the affected 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.1.2

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 installed Flowise version
    Check the Flowise version by examining package.json in the installation directory, or run 'npm list flowise' or check the UI footer which often displays the version number
    Affected if Version is before 3.1.2 (e.g., 3.1.1, 3.1.0, earlier versions)
  2. Verify E2B_APIKEY configuration
    Check if the E2B_APIKEY environment variable is set on the Flowise server. On Linux, run 'env | grep E2B_APIKEY'; on Windows, run 'Get-ChildItem Env: | Where-Object {$_.Name -eq "E2B_APIKEY"}'
    Affected if E2B_APIKEY is not set (empty or undefined) - this is the default vulnerable configuration
  3. Confirm Custom JS Function node is in use
    Review Flowise chatflows or flows that utilize the Custom JS Function node by examining the flow configuration files or the Flowise database for nodes of type 'customJSFunction'
    Affected if Custom JS Function node is actively used in any deployed flow
  4. Check API endpoint accessibility
    Attempt a POST request to /api/v1/node-custom-function with a valid authentication token or API key. If the request is accepted and processes JavaScript code, the endpoint is exposed
    Affected if The endpoint accepts requests from any authenticated user or API key without additional authorization checks
  5. Review API key access controls
    Examine user accounts and API keys in Flowise to determine which users possess API access. Check if any low-privilege users have API key permissions
    Affected if Users with limited permissions or any API key holder can access the vulnerable endpoint

You are affected if Flowise version is before 3.1.2 AND E2B_APIKEY is not configured AND the Custom JS Function node is accessible to authenticated users or API keys.

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.2 or later
Fixed in 3.1.2
Interim mitigation

Upgrade to Flowise version 3.1.2 or later. If upgrading is not immediately possible, ensure E2B_APIKEY is properly configured to avoid using the vulnerable NodeVM sandbox, and implement additional authentication controls on the affected endpoint.

Recommended fix High confidence

3.1.2

  1. 1. Back up your current Flowise configuration and data
  2. 2. Stop the running Flowise instance
  3. 3. Update Flowise to version 3.1.2 or later
  4. 4. Verify the installation was successful by checking the version
  5. 5. Restart the Flowise service
  6. 6. Test that the /api/v1/node-custom-function endpoint now requires proper authorization
  7. 7. Confirm the NodeVM sandbox is no longer used when E2B_APIKEY is not configured

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

Fix this in Flowise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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