# CVE-2026-91929: Flowise before 3.1.4 Cross-Tenant Authorization Bypass

> Attackers with Enterprise access can bypass authorization to delete workspaces, modify roles, and abuse SSO secrets across tenants.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:L/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:** 15 Sep 2026
- **Also known as:** GHSA-397m-c2vg-wm77, GHSA-7x8x-vv46-4579

## What is CVE-2026-91929?

CVE-2026-91929 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 versions before 3.1.4 contain cross-tenant authorization gaps in Enterprise endpoints that fail to verify resource ownership before operations. Attackers with Enterprise access can delete arbitrary workspaces, invite themselves into other organizations, modify cross-org roles, and abuse stored SSO secrets.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-91929 being exploited?

There is no known exploitation of CVE-2026-91929 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91929 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: There is no known exploitation of CVE-2026-91929 in the wild and no public exploit code.

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-91929/ (Markdown: https://insights.sbomify.com/CVE-2026-91929/index.md)
```

## Sources

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

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