dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-46478

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, DatasetRow create and update mass-assignment allows cross-workspace row 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 versions prior to 3.1.2 contain a mass-assignment vulnerability in the DatasetRow create and update operations. The application does not properly restrict which fields can be modified, allowing authenticated users to manipulate ownership or workspace assignment fields and take over rows belonging to other workspaces.

MitigationUpgrade Flowise to version 3.1.2 or later. If immediate upgrade is not possible, implement explicit allow-listing of permitted fields in DatasetRow API operations and verify workspace access controls.

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 the installed Flowise version
    Run 'npm list flowise' or check the package.json file in your Flowise installation directory for the version field
    Affected if The version listed is below 3.1.2 (for example, 3.1.1, 3.1.0, or any version starting with 3.0.x)
  2. Confirm Flowise API is accessible
    Verify the Flowise service is running and the API endpoint is reachable (typically at the default port 3000 or your configured port)
    Affected if The API responds to requests, indicating the application is active and the attack surface exists
  3. Check for multiple workspace configuration
    Examine your Flowise configuration or database for the presence of more than one workspace, or look for workspace-related tables/records in your database
    Affected if Multiple workspaces exist in the system, creating the condition for cross-workspace exploitation
  4. Verify user authentication is enabled
    Check if authentication is configured in your Flowise instance (look for AUTH_MODE settings or user/login configuration)
    Affected if User authentication is enabled, meaning authenticated users could attempt the cross-workspace row modification
  5. Confirm DatasetRow feature is in use
    Look for dataset row tables or records in your Flowise database, or check if any flows or integrations use the Dataset functionality
    Affected if Dataset rows exist in the system, indicating the vulnerable create/update operations could be targeted

You are affected if you are running any Flowise version below 3.1.2 with multiple workspaces and DatasetRow data present, where authenticated users could exploit the mass-assignment flaw to access rows outside their authorized 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 Flowise to version 3.1.2 or later. If immediate upgrade is not possible, implement explicit allow-listing of permitted fields in DatasetRow API operations and verify workspace access controls.

Recommended fix High confidence

Flowise 3.1.2

  1. Stop the running Flowise instance to prevent data corruption during upgrade
  2. Backup your existing Flowise data and configuration files (database, .env file, any custom configurations)
  3. If using Docker: Pull the latest image with tag 3.1.2 (docker pull flowiseai/flowise:3.1.2) and recreate your container with the updated image
  4. If using npm: Run 'npm install -g [email protected]' to update to the patched version
  5. If using Docker Compose: Update the image tag to 3.1.2 in your docker-compose.yml and recreate containers
  6. After upgrade, verify the Flowise service starts successfully
  7. Test that DatasetRow create and update operations respect workspace boundaries as expected
  8. Monitor logs for any errors during startup and initial operations
Caveat Minor patch update - should not introduce breaking changes; review release notes for any minor behavior changes

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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