dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-46480

HIGH · 8.8 CVSS v3.1 Published 2026-06-08
Fix available
A fix is available. Upgrade to 3.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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, evaluator create and update mass-assignment allows cross-workspace evaluator takeover. 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 prior to version 3.1.2 contains a mass-assignment vulnerability in the evaluator create and update endpoints that allows attackers to modify evaluator attributes they should not have access to, enabling cross-workspace evaluator takeover due to improper authorization controls.

MitigationUpgrade to Flowise version 3.1.2 or later, which patches the mass-assignment vulnerability and implements proper workspace isolation for evaluator operations.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Flowise version
    Check the package.json file in the Flowise installation directory, or run 'npm list flowise' or check the Docker image tag if running containerized
    Affected if The installed version is prior to 3.1.2 (e.g., 3.1.1, 3.1.0, earlier releases)
  2. Determine if evaluator feature is in use
    Inspect the Flowise application for any created evaluators - look in the database or UI for documents or records labeled as evaluators
    Affected if Any evaluator records exist in the system, as the vulnerability affects create and update operations on this entity
  3. Verify multi-workspace configuration
    Check Flowise configuration settings or database for evidence of multiple workspace definitions - look for workspace-related tables or configuration keys
    Affected if More than one workspace is configured, as the flaw enables cross-workspace evaluator manipulation
  4. Inspect evaluator access patterns
    Query the evaluator records in the database and compare the workspace ID assigned to each evaluator against the workspace IDs of the users who created or modified them
    Affected if Any evaluator exists where the modifying user's assigned workspace differs from the evaluator's workspace, indicating potential unauthorized cross-workspace access

You are affected if Flowise version is below 3.1.2 AND the evaluator feature is enabled with multiple workspaces in use, as the vulnerability allows authenticated users to modify evaluators outside their assigned workspace.

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, which patches the mass-assignment vulnerability and implements proper workspace isolation for evaluator operations.

Recommended fix High confidence

Flowise version 3.1.2

  1. 1. Backup your current Flowise installation and any associated data
  2. 2. Stop the Flowise service if it's currently running
  3. 3. If installed via npm, run: npm install -g [email protected]
  4. 4. If using Docker, update your image tag to the version 3.1.2 and recreate the container
  5. 5. After upgrading, verify the service starts successfully
  6. 6. Test evaluator creation and update functionality to confirm the mass-assignment vulnerability is resolved
  7. 7. Review evaluator objects to ensure no unauthorized cross-workspace access has occurred

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
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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