CVE-2026-41267
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 3.1.0, an improper mass assignment (JSON injection) vulnerability in the account registration endpoint of Flowise Cloud allows unauthenticated attackers to inject server-managed fields and nested objects during account creation. This enables client-controlled manipulation of ownership metadata, timestamps, organization association, and role mappings, breaking trust boundaries in a multi-tenant environment. This vulnerability is fixed in 3.1.0.
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 confidenceThis is an improper mass assignment (over-posting) vulnerability in Flowise's account registration endpoint. Unauthenticated attackers can inject server-managed fields and nested objects via JSON during account creation, allowing manipulation of ownership metadata, timestamps, organization associations, and role mappings. This breaks trust boundaries in the multi-tenant environment by enabling privilege escalation.
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.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check the installed Flowise versionLocate the Flowise installation and identify the version number (typically found in package.json, a version file, or via a /version API endpoint if exposed). Compare this to the affected range: versions prior to 3.1.0.Affected if The installed version is less than 3.1.0
-
Verify whether account registration is publicly accessibleDetermine if the user registration endpoint (typically at /api/v1/user/create or similar POST endpoint for account creation) is exposed to unauthenticated network access without any CAPTCHA, rate limiting, or invite-only restrictions.Affected if The registration endpoint is publicly accessible without authentication requirements
-
Inspect API configuration for field allow-listingReview the API endpoint configuration or middleware for the registration route. Check if there is explicit allow-listing of permitted input fields, or if all incoming JSON payload fields are blindly accepted and passed to the user creation logic.Affected if There is no strict allow-listing enforcement; all JSON fields from the request are mapped to user objects without filtering
-
Review application logs for abnormal registration patternsExamine Flowise application logs (typically in logs/ or stdout) for unusual account creation patterns, such as bulk registrations or requests containing unexpected nested fields like roles, organizationId, or createdAt.Affected if Logs show registration attempts with injected server-managed fields (e.g., role, orgId, timestamps) that were not intended to be user-controllable
The environment is affected if Flowise is running a version lower than 3.1.0 AND the account registration endpoint is exposed to unauthenticated users without strict input validation.
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.0
Upgrade to Flowise 3.1.0 or later. If immediate upgrade is not possible, implement strict allow-listing of permitted user-input fields in the registration endpoint to prevent injection of server-managed parameters.
3.1.0
- 1. Back up your current Flowise configuration and data
- 2. Upgrade Flowise to version 3.1.0 or later
- 3. Verify the upgrade was successful by checking the Flowise version
- 4. Test the account registration functionality to confirm the vulnerability is resolved
- 5. Review audit logs for any suspicious account creation activity that may have occurred prior to the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41267 — 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-41267 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