# CVE-2026-100608: Flowise through 3.1.4 Authorization Bypass via BullMQ Dashboard

> Authenticated users can access the BullMQ dashboard to view and modify cross-tenant job data and configurations due to missing authorization checks.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 26 Sep 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-c52g-w44q-cg6m, GHSA-rpcc-gw54-mfgx

## What is CVE-2026-100608?

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

### Official description

Flowise through 3.1.4 does not enforce authorization on the BullMQ admin dashboard. When the server runs in queue mode with the dashboard enabled and not in cloud mode (MODE=queue, ENABLE_BULLMQ_DASHBOARD=true, and !isCloud()), the /admin/queues mount is protected only by the verifyTokenForBullMQDashboard middleware, which validates the JWT but performs no role, permission, or workspace/organization scoping check; the mount also lies outside /api/v1/* so the global API gate does not apply. As a result, any authenticated user — including the lowest-privileged member of any tenant — can reach the full Bull-Board UI and view all queues and job payloads across the entire instance, including chat inputs and overrideConfig (which may carry credentials and prompts), chatflow.flowData graph definitions with custom function source code, credential IDs and system prompts, chatIds, files, and the originating orgId/workspaceId. The dashboard's write actions (retry, remove, promote, clean) are likewise usable across tenants. No patched version is available as of the advisory.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-100608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100608 is a high-severity missing authorization vulnerability in FlowiseAI Flowise, published on 26 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-100608 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-100608/ (Markdown: https://insights.sbomify.com/CVE-2026-100608/index.md)
```

## Sources

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

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