CVE-2026-46477
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 · uneditedFlowise is a drag & drop user interface to build a customized large language model flow. Prior to version 3.1.2, dataset create and update mass-assignment allows cross-workspace dataset 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 · moderate confidenceFlowise versions prior to 3.1.2 contain a mass-assignment vulnerability in dataset create and update endpoints. The application does not properly restrict which fields can be modified, allowing authenticated users to specify parameters such as workspace ownership and takeover datasets belonging to other workspaces.
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< 3.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Flowise installationCheck if Flowise is running in your environment by reviewing running node.js processes, Docker containers, or the application startup logs for 'flowise' references.Affected if Flowise is not present in the environment.
-
Determine installed Flowise versionCheck the package.json file in the Flowise installation directory for the version field, or run 'npm list flowise' or 'docker images' to retrieve the installed version.Affected if The installed version is lower than 3.1.2 (e.g., 3.1.1, 3.1.0, earlier versions).
-
Verify multi-workspace usageReview Flowise configuration files (config/*.yaml or config/*.json) or environment variables for workspace-related settings, and check if multiple workspaces exist in the database.Affected if Multiple workspaces are configured and active in the Flowise instance.
-
Inspect dataset API endpointsReview the Flowise API documentation or source code for dataset create (POST /api/v1/datasets) and update (PUT /api/v1/datasets/:id) endpoints to confirm they accept workspace-related parameters.Affected if The dataset endpoints accept a workspace_id or similar parameter without server-side ownership validation.
A user is affected if Flowise version is below 3.1.2 and the dataset feature with multi-workspace isolation is in use, allowing any authenticated user to modify datasets outside their assigned workspace.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.2
Upgrade to Flowise version 3.1.2 or later, which implements proper field allowlisting for dataset operations.
3.1.2
- Backup your Flowise data and configuration before upgrading
- Stop the Flowise service
- Update Flowise to version 3.1.2. If installed via npm, run: npm install [email protected]
- If using Docker, pull the new image with the tag for version 3.1.2
- Start the Flowise service with the updated version
- Verify the upgrade was successful by checking the Flowise version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-46477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-46477 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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