CVE-2026-90533: Flowise broken access control vulnerability
Flowise
An access control flaw in Flowise allows authenticated members to retrieve organization owners' full records, including password hashes. The issue is resolved in versions prior to and including 3.1.4.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 6.5
- EPSS
- <0.01 · top 73% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 12 Sep 2026
- last update
- 12 Sep 2026
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2026-09-12CVE-2026-90533: Flowise before 3.1.4 contains a broken access control vulnerability in GET /api/v1/organizationuser that allows any authenticated…NVD · nvd.nist.gov/vuln/detail/CVE-2026-90533
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- dates
- happened 12 Sep 2026 · first reported 12 Sep 2026
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2026-90533: Flowise broken access control vulnerability https://gcdradar.vercel.app/incidents/cve-2026-90533-flowise-broken-access-control-vulnerability · AIR-2026-1373 · closed 2026-09-12 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2026-09-12 - AI role: Attack on AI - Products: Flowise - CVE ids: CVE-2026-90533 - CVSS: 6.5 ## Summary An access control flaw in Flowise allows authenticated members to retrieve organization owners' full records, including password hashes. The issue is resolved in versions prior to and including 3.1.4. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2026-09-12: CVE-2026-90533: Flowise before 3.1.4 contains a broken access control vulnerability in GET /api/v1/organizationuser that allows any authenticated… (https://nvd.nist.gov/vuln/detail/CVE-2026-90533) ## Sources - 2026-09-12 NVD: CVE-2026-90533: Flowise before 3.1.4 contains a broken access control vulnerability in GET /api/v1/organizationuser that allows any authenticated… https://nvd.nist.gov/vuln/detail/CVE-2026-90533 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed7.5Flowise Flowise Missing RBAC on Chat Endpoints Permits Unauthorized Data Access
Patch now · Disclosed · since 26 Sep 2026 · CVE-2026-100605
AI - closed9.2Flowise Flowise Authentication Vulnerability Allows Account Takeover via Email Matching
Patch now · Disclosed · No patch yet · since 26 Sep 2026 · CVE-2026-100607
AI - closed9.2Flowise CVE-2026-100606: Flowise enterprise mode SSO login authentication bypass
Patch now · Disclosed · since 26 Sep 2026 · CVE-2026-100606
AI - closed7.6Flowise CVE-2026-100609: Flowise credential lookup lacks workspace isolation
Patch now · Disclosed · since 26 Sep 2026 · CVE-2026-100609
AI - closed8.7Flowise CVE-2026-100608: Flowise lacks proper authorization on BullMQ admin dashboard
Patch now · Disclosed · since 26 Sep 2026 · CVE-2026-100608
AI - closed7.7Flowise CVE-2026-100610: Flowise missing permission checks on upsert-history endpoints
Patch now · Disclosed · since 26 Sep 2026 · CVE-2026-100610
AI