All vulnerabilities

Servers and applications

GHSA-rpcc-gw54-mfgx

BullMQ dashboard `/admin/queues` is auth-only (no RBAC), exposing cross-tenant job payloads to every authenticated user

Severity
High 8.7
Published
10 Sept 2026
Last changed
10 Sept 2026
Added to UpHeron
1 Nov 2026
Weakness
Improper privilege management (CWE-269)Missing authorization (CWE-862)Incorrect authorization (CWE-863)
Attack
Over the network · Needs a user account · No user action needed
Attacker can
Read data · Change data · Slow it down
CVSS vector
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
Sources
Project advisories (GitHub)

Description

When Flowise runs in queue mode with the BullMQ admin dashboard enabled (MODE=queue + ENABLE_BULLMQ_DASHBOARD=true + !isCloud()), the /admin/queues mount is gated only by the verifyTokenForBullMQDashboard middleware (enterprise/middleware/passport/index.ts:437-463). That middleware accepts any authenticated user — there is no role check, no permission check, no workspace/organization scoping. Every workspace member, including the lowest-privileged role of any tenant, reaches the full Bull-Board UI which exposes:

  • All queues across the entire Flowise instance (prediction, upsertion).
  • All job payloads — including incomingInput (chat messages plus overrideConfig which can carry credentials and prompts), the entire chatflow.flowData (graph definition with customFunction.javascriptFunction source code, credential IDs, system prompts, tool configurations), the chatId, files, and the orgId/workspaceId of the originating tenant.
From FlowiseAI/Flowise's security advisory. Shortened; the full text is there.

Workarounds

  • Set ENABLE_BULLMQ_DASHBOARD to anything other than true (or unset it). The dashboard then will not be mounted at all and Flowise in queue mode continues to function — only the inspection UI is disabled.
  • If the dashboard is required for operational use, restrict access at the network layer (e.g., a reverse proxy that gates /admin/queues/* on a VPN allow-list or a separate IdP-signed cookie) until the upstream RBAC check ships.
Workarounds as given by FlowiseAI/Flowise's security advisory.

Affected software

SoftwareAffected versions
FlowiseServers and applications · github:flowiseai/flowise
  • Every version up to 3.1.4

About Flowise

Build AI Agents, Visually

From its GitHub repository.
Archived
Yes, no longer maintainedGitHub
Weekly downloads (npm)
6,604npm, 15 Nov 2026
Docker Hub pulls
7,390,661Docker Hub, 15 Nov 2026
GitHub stars
55,573GitHub, 15 Nov 2026
Forks
25,094GitHub, 15 Nov 2026
Latest release
[email protected]GitHub, 15 Nov 2026
Released
29 Jul 2026GitHub
First published on GitHub
31 Mar 2023GitHub

References