Skip to main content
Vulnerability Database/CVE-2026-100608

CVE-2026-100608: Flowise BullMQ Auth Bypass Vulnerability

CVE-2026-100608 is an authorization bypass flaw in Flowise through version 3.1.4 affecting the BullMQ admin dashboard. Any authenticated user can access sensitive data across tenants. This post covers technical details, affected versions, impact, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100608 Overview

CVE-2026-100608 is a missing authorization vulnerability [CWE-862] in Flowise through version 3.1.4. The flaw affects the BullMQ admin dashboard mounted at /admin/queues when the server runs in queue mode with the dashboard enabled outside cloud mode. The verifyTokenForBullMQDashboard middleware validates JWTs but performs no role, permission, workspace, or organization scoping checks. Any authenticated low-privileged tenant member can access the full Bull-Board UI across the entire instance. Exposed data includes chat inputs, overrideConfig payloads, chatflow.flowData graph definitions, credential IDs, system prompts, chat identifiers, files, and originating orgId/workspaceId values. No patched version was available at advisory publication.

Critical Impact

Authenticated tenants of any privilege level can read and modify queue data across all tenants, exposing credentials, prompts, custom function source code, and chat payloads.

Affected Products

  • Flowise versions up to and including 3.1.4
  • Instances running with MODE=queue and ENABLE_BULLMQ_DASHBOARD=true
  • Self-hosted deployments where isCloud() returns false

Discovery Timeline

  • 2026-09-26 - CVE-2026-100608 published to NVD
  • 2026-09-26 - Last updated in NVD database

Technical Details for CVE-2026-100608

Vulnerability Analysis

Flowise exposes a BullMQ administration interface via Bull-Board at /admin/queues when operating in distributed queue mode. The route sits outside the /api/v1/* namespace, so the global API authorization gate that enforces tenant scoping does not apply. The only guard in place is verifyTokenForBullMQDashboard, which confirms a valid JWT but ignores the authenticated principal's role, workspace, or organization context.

Bull-Board exposes every queue and job payload managed by the Flowise worker pool. In a multi-tenant deployment, jobs from all organizations share the same Redis-backed queues. Any authenticated user can therefore enumerate jobs belonging to other tenants and read their contents directly from the UI.

Root Cause

The root cause is a missing authorization check [CWE-862] in the middleware chain protecting the Bull-Board mount. Authentication is conflated with authorization: the presence of a valid token is treated as sufficient to access an administrative interface that should be restricted to platform operators. Tenant isolation primitives available elsewhere in the API are not applied to the dashboard route.

Attack Vector

An attacker authenticates as the lowest-privileged member of any tenant on the Flowise instance. The attacker then navigates to /admin/queues and loads the Bull-Board interface. From there, they can enumerate queues, inspect job payloads containing chat inputs, overrideConfig values that may carry credentials and prompts, and chatflow.flowData graph definitions that include custom function source code. Write actions such as retry, remove, promote, and clean are also accessible, allowing cross-tenant job manipulation. See the VulnCheck Advisory on Flowise for additional technical context.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-100608

Indicators of Compromise

  • Access log entries showing requests to /admin/queues from accounts that are not platform administrators.
  • HTTP responses from /admin/queues/api/queues returning job payloads to standard tenant users.
  • Unexpected retry, remove, promote, or clean actions issued against BullMQ queues outside the acting user's workspace.

Detection Strategies

  • Review reverse proxy and application logs for all requests to the /admin/queues path and correlate the authenticated user ID against the expected administrative account list.
  • Alert on any access to the BullMQ dashboard originating from users whose orgId or workspaceId does not match the job records being viewed.
  • Audit BullMQ job history for state transitions triggered by non-administrative principals.

Monitoring Recommendations

  • Enable verbose request logging on the Flowise reverse proxy for the /admin/* path prefix.
  • Centralize Flowise and Redis logs into a SIEM and build detections keyed to /admin/queues access and JWT subject metadata.
  • Monitor for enumeration patterns such as rapid, sequential retrieval of job IDs across multiple queues by a single session.

How to Mitigate CVE-2026-100608

Immediate Actions Required

  • Set ENABLE_BULLMQ_DASHBOARD=false on all self-hosted Flowise instances that run in queue mode.
  • Restrict network access to /admin/queues using a reverse proxy allowlist limited to administrator IP ranges.
  • Rotate credentials, API keys, and system prompts that may have been exposed through job payloads.
  • Audit multi-tenant deployments for cross-tenant access to the Bull-Board interface since deployment.

Patch Information

No patched Flowise release is available as of the advisory. Monitor the GitHub Security Advisory for upstream fix availability and apply the vendor-supplied update when published.

Workarounds

  • Disable the BullMQ dashboard entirely by unsetting or setting ENABLE_BULLMQ_DASHBOARD to false.
  • Place the /admin/queues route behind a separate authentication layer such as an identity-aware proxy or HTTP basic auth enforced at the reverse proxy.
  • Segment the Flowise administrative interface onto a management-only network that tenants cannot reach.
  • If the dashboard must remain enabled, deploy a per-tenant Flowise instance so that queue contents are not shared across organizations.
bash
# Configuration example: disable the BullMQ dashboard
export ENABLE_BULLMQ_DASHBOARD=false
# Restart the Flowise service after updating the environment variable

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.