dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-46475

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, assistant create and update mass-assignment allows cross-workspace assistant 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 assistant create and update endpoints. This allows authenticated users to modify the workspace association of assistants, enabling cross-workspace assistant takeover where an attacker can seize control of assistants belonging to other workspaces.

MitigationUpgrade Flowise to version 3.1.2 or later to patch the mass-assignment vulnerability. Additionally, implement proper authorization checks on assistant create/update operations to verify workspace ownership.

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 Flowise installation and version
    Locate the Flowise installation and determine the installed version by checking package.json, Docker image tag, or running 'npm list flowise' if installed locally. Compare this version to the 3.1.2 threshold.
    Affected if The installed Flowise version is below 3.1.2 (e.g., 3.1.1, 3.1.0, earlier releases).
  2. Verify assistant API endpoint accessibility
    Check if the Flowise server exposes the assistant create and update endpoints (typically under /api/v1/assistants or similar paths). Review server configuration or API documentation to confirm these endpoints are enabled.
    Affected if The assistant create and update endpoints are exposed and reachable over the network.
  3. Confirm authentication is enforced on endpoints
    Review Flowise authentication settings in the configuration file or environment variables (look for AUTH settings, API key configuration, or session-based auth setup). Verify that unauthenticated requests to assistant endpoints are rejected.
    Affected if Authentication is enabled but the assistant endpoints accept requests from any authenticated user regardless of their workspace permissions.
  4. Inspect for unauthorized assistant modifications
    Review Flowise application logs for API calls to assistant create/update endpoints. Look for requests that modify the workspace field or workspaceId parameter of assistants, especially where the workspace differs from the user's assigned workspace.
    Affected if Logs show assistant create or update API calls that change workspace associations, indicating exploitation attempts.
  5. Audit workspace isolation in assistant records
    Query the Flowise database or API to list all assistants and their associated workspace IDs. Identify any assistants where the workspace ID differs from expected values or where assistants are unexpectedly shared across workspaces.
    Affected if Assistants exist with workspace associations that do not match the creating user's primary workspace, suggesting potential cross-workspace takeover.

A user is affected if Flowise version is below 3.1.2 AND the assistant create/update API endpoints are accessible to authenticated users without strict workspace-boundary enforcement.

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 to patch the mass-assignment vulnerability. Additionally, implement proper authorization checks on assistant create/update operations to verify workspace ownership.

Recommended fix High confidence

Flowise version 3.1.2

  1. Backup your Flowise installation and data before upgrading
  2. Stop the running Flowise instance
  3. Upgrade Flowise to version 3.1.2 using your package manager or deployment method
  4. Restart Flowise and verify the application runs correctly
  5. Test that assistants can be created and updated without cross-workspace access

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

Fix this in Flowise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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