Owner account takeover via unsanitized user record
Published Sep 12, 2026 · Updated Sep 12, 2026
Broken access control in Flowise before 3.1.4 allows remote authenticated users to retrieve the organization owner's full user record. OrganizationUserService assigned the owner's unsanitized user entity to the response instead of passing a copy through sanitizeUser. Any authenticated organization member can supply a user ID, obtain the owner's bcrypt hash and temporary tokens, and use cracked credentials to take over the highest-privileged account.
Summary
What happened
Broken access control in Flowise before 3.1.4 allows remote authenticated users to retrieve the organization owner's full user record. OrganizationUserService assigned the owner's unsanitized user entity to the response instead of passing a copy through sanitizeUser. Any authenticated organization member can supply a user ID, obtain the owner's bcrypt hash and temporary tokens, and use cracked credentials to take over the highest-privileged account.
The record
- CVE
- CVE-2026-90533
- Published
- Sep 12, 2026
- Updated
- Sep 12, 2026
- Vendor
- FlowiseAI
- Product
- Flowise
- Classifications
- T1555
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 12, 2026CVE publishedPublication date reported by the CVE source.
- Sep 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo