dbcve.org
FlowiseApplication · Flowiseai

CVE-2026-46476

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, CustomTemplate create and update mass-assignment allows cross-workspace template 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 CustomTemplate create and update endpoints. This allows authenticated users to modify or create templates in workspaces they don't have authorization for, enabling cross-workspace template takeover.

MitigationUpgrade Flowise to version 3.1.2 or later to apply the patch that addresses the mass-assignment vulnerability in CustomTemplate 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. Check installed Flowise version
    Run 'npm list flowise' or check package.json, or query the /api/v1/version endpoint if available
    Affected if Version is below 3.1.2 (e.g., 3.1.0, 3.0.x, etc.)
  2. Identify if CustomTemplate endpoints are exposed
    Review API routing configuration or server logs for POST/PUT requests to paths like /api/v1/custom-templates or /api/custom-template/create and /api/custom-template/update
    Affected if The CustomTemplate create/update endpoints are accessible to authenticated users in your environment
  3. Check if multi-workspace feature is enabled
    Inspect Flowise configuration (config.yaml, .env file, or admin settings) for workspace-related settings such as MULTI_TENANT, WORKSPACE_ENABLED, or similar flags
    Affected if Multiple workspaces are configured and users from one workspace can interact with templates from another workspace
  4. Audit CustomTemplate ownership records
    Query the database or API for CustomTemplate records and check the 'workspaceId' or 'ownerWorkspace' field against the user making the request
    Affected if Templates exist where the requesting user's workspace differs from the template's assigned workspace, indicating potential exploitation

You are affected if Flowise version is below 3.1.2 AND the CustomTemplate API endpoints are accessible to authenticated users, particularly in multi-workspace deployments.

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 apply the patch that addresses the mass-assignment vulnerability in CustomTemplate operations.

Recommended fix High confidence

Flowise version 3.1.2

  1. 1. Back up your Flowise database and configuration files before upgrading.
  2. 2. Stop the running Flowise service.
  3. 3. If using Docker: Pull the latest Flowise image with tag 3.1.2 (docker pull flowiseai/flowise:3.1.2) and recreate your container.
  4. 4. If using npm: Run 'npm install [email protected]' to install the patched version.
  5. 5. Verify the installed version matches 3.1.2 using 'flowise --version' or checking the UI.
  6. 6. Start the Flowise service and verify all CustomTemplate functionality operates correctly.
  7. 7. Confirm the mass-assignment vulnerability is resolved by testing CustomTemplate create and update operations across workspaces.

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

Fix this in Flowise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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