# CVE-2026-91933: Flowise before 3.1.4 Authorization Bypass via openai-realtime

> Authenticated users can bypass workspace restrictions to access and execute tools from other workspaces, leading to data exposure and side effects.

- **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:** 17 Sep 2026
- **Also known as:** GHSA-g5x4-4x4f-qgq9, GHSA-gggp-6qmf-xwwc

## What is CVE-2026-91933?

CVE-2026-91933 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 enforce workspace-level authorization checks in openai-realtime endpoints, allowing authenticated users to access tools from ChatFlows in other workspaces by supplying an unscoped chatflowid. Attackers can invoke GET and POST requests to retrieve tool definitions and execute tools from victim workspaces, triggering external side effects and accessing sensitive tool outputs.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-91933 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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