CVE-2026-90533
Received Received - Intake

Broken Access Control in Flowise Exposes Owner Credentials

Vulnerability report for CVE-2026-90533, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-12

Last updated on: 2026-09-12

Assigner: VulnCheck

Description

Flowise before 3.1.4 contains a broken access control vulnerability in GET /api/v1/organizationuser that allows any authenticated organization member to retrieve the organization owner's full user record including bcrypt password hash and temporary tokens. Attackers can query the endpoint with any user ID to obtain the owner's credential hash for offline cracking, enabling account takeover of the highest-privileged account.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-12
Last Modified
2026-09-12
Generated
2026-09-12
AI Q&A
2026-09-12
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
flowiseai flowise to 3.1.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-90533 is a broken access control vulnerability in Flowise versions 3.1.3 and earlier. It affects the GET /api/v1/organizationuser endpoint, allowing any authenticated organization member to retrieve the owner's full user record, including bcrypt password hash and temporary tokens. The flaw occurs because the endpoint lacks proper permission checks and does not scrub sensitive fields like the password hash.

Detection Guidance

To detect this vulnerability, check if your Flowise instance is running a version before 3.1.4. Use commands like 'curl -X GET http://<target>/api/v1/organizationuser?userId=<any_user_id>' to test if the endpoint returns sensitive data such as bcrypt password hashes or tokens.

Impact Analysis

An attacker with low-privilege access can exploit this to obtain the organization owner's password hash. They can then crack the hash offline to gain full control of the highest-privileged account. This enables complete takeover of the organization's Flowise instance, including access to all data and functions.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection requirements and HIPAA's security rules. It may result in data breaches, unauthorized disclosure of personal or health information, and failure to maintain confidentiality and integrity of sensitive records.

Mitigation Strategies

Immediately upgrade Flowise to version 3.1.4 or later. If upgrading is not possible, restrict access to the /api/v1/organizationuser endpoint and implement proper authentication and authorization checks to prevent unauthorized access to sensitive user records.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-90533. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart