# CVE-2026-91930: Flowise before 3.1.4 Cross-Tenant Organization Admin Takeover

> Authenticated users can bypass tenant isolation to gain administrative access to other organizations by manipulating organization IDs.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 20 Sep 2026
- **Also known as:** GHSA-2jfv-qfvv-395r, GHSA-pprx-4prj-35mj

## What is CVE-2026-91930?

CVE-2026-91930 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Flowise before 3.1.4 fails to scope enterprise organization and workspace membership APIs to the caller's tenant, allowing authenticated users to supply arbitrary organization IDs. Attackers can add themselves as organization owners, create workspaces, and gain administrative access to victim organizations by exploiting insufficient tenant isolation in the organizationuser and workspace endpoints.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-91930?


## How do I fix CVE-2026-91930?

No fix has been published for CVE-2026-91930 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-91930 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91930 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-91930 and fix it if it is affected.

What it is: CVE-2026-91930 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91930 exists.

Affected product: FlowiseAI Flowise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-91930/ (Markdown: https://insights.sbomify.com/CVE-2026-91930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-91930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-91930
- OSV: https://osv.dev/vulnerability/CVE-2026-91930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-91930/
Summaries are generated and may contain mistakes; the official description above is the record.