CVE-2026-90533

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-12 13:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-15 18:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.0 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-09-12 13:16 UTC

Last modified

2026-09-15 18:23 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-862 · Missing authorization

Record status

Analyzed

Affected

• Flowiseai Flowise < 3.1.4

Attack profile CVSS 4.0 · 6.0

Attack vector

Network

Complexity

High

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-90533.md and follow it. Check whether this project is affected by CVE-2026-90533. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge