CVE-2026-41267 is a high severity mass assignment flaw (CVSS 8.1) in the Flowise account registration endpoint. Before 3.1.0, an unauthenticated caller can inject server managed fields, such as organization and role mappings, during sign up. The fix is Flowise 3.1.0.
What's affected
The record describes the registration endpoint of Flowise Cloud. The GitHub advisory lists the npm package flowise at 3.0.13 and earlier, with 3.1.0 as the patched version. If you self host a multi-user build with registration enabled, check the same version.
How to check if you're exposed
npm ls flowise
For container installs, check the tag. Then ask whether public registration is enabled and whether your deployment uses organizations and workspaces. A single user, private instance with sign up disabled has far less exposure.
Next, review your user table for accounts you do not recognise, and for users with unexpected organization or role links. Dates that look wrong, such as creation times far in the past, are a signal worth checking.
What to do now
- Upgrade Flowise to 3.1.0 or later.
- Disable open registration if you do not need it.
- Audit accounts, organizations and role assignments created while an affected version was online.
- Remove or correct any account that has memberships it should not have.
Why it matters
The record lists CWE-639, authorization bypass through a user controlled key, and CWE-915, improperly controlled modification of dynamically determined object attributes. That second one is the textbook name for mass assignment.
The advisory explains that the backend maps client JSON straight into internal models instead of using a strict allowlist. Fields like ownership, timestamps, organization and role were saved as the client sent them. In a multi-tenant product, that turns a sign up form into a way to pick your own tenant and role. The cure is a fixed input schema for every write endpoint. The record does not flag this CVE as known exploited.
Quick check
Why is the score lower than the other Flowise bugs?
The vector marks attack complexity as high, which lowers the number to 8.1. It still needs no login and no user action.
Sources
Last reviewed: 19 October 2026.
