CVE-2026-86005 · Package
NO FIX YET · SEE WHAT TO DO
Chartbrew mounts its BullMQ queue administration dashboard at /apps/queues without an authentication check. A remote attacker who can reach that route can read job payloads and logs and, depending on the Bull Board version and queue state, retry or delete jobs.
first public Sep 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Instances of Chartbrew before 5.2.3 where Redis and BullMQ are enabled and the /apps/queues route is reachable, because a reverse proxy does not block it. The dashboard relied on network reachability as its only access control. Deployments with Redis/BullMQ disabled, or with the route blocked at the proxy or behind another authentication layer, are less exposed.
Not affected if redis-disabled, route-blocked-at-proxy, version-5.2.3-or-later
Who cares bullmq, chartbrew, redis, self-hosted
5.2.3 are affected/apps/queues from outside your network and see whether the dashboard loads without login/apps/queues5.2.3 or laterChartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, the administrative BullMQ dashboard was mounted without an authentication check. The vulnerable surface is the Bull Board/BullMQ administration dashboard at /apps/queues. A remote unauthenticated attacker reaches /apps/queues on a Chartbrew instance where Redis and BullMQ are enabled and a reverse proxy does not independently block the route. The dashboard trusted network reachability as authorization and exposed its queue-management interface directly. Redis and BullMQ must be enabled and the route must be reachable. Available actions depend on the installed Bull Board version and queue state, while confidentiality depends on job payload and log contents. An unauthenticated user can inspect exposed job payloads and logs and, when enabled by the installed version and queue state, retry or delete jobs or otherwise alter queue processing, affecting confidentiality, integrity, or availability. This issue is fixed in version 5.2.3.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.