Chartbrew: Unauthenticated BullMQ Admin Dashboard Exposure in Chartbrew
Affects Chartbrew before 5.2.3 when Redis and BullMQ are enabled and the backend is network-accessible without a reverse proxy blocking /apps/queues. Fixed in 5.2.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 5.2.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 5.2.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Chartbrew, an open-source app for building charts from databases and APIs, exposes its BullMQ admin dashboard at /apps/queues without an authentication check, so anyone who can reach that route over the network, without logging in, can view job payloads and logs and may be able to retry or delete jobs or otherwise change queue processing. This needs a setup where Redis and BullMQ are enabled and no reverse proxy blocks the route.
Read the original description
Chartbrew 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 5.2.3.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- chartbrew chartbrew
fixed in 5.2.3
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-86005
Is CVE-2026-86005 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The BullMQ admin dashboard at /apps/queues can be reached without logging in. It exposes internal queue information and job payloads and logs, and could allow jobs to be retried, deleted, modified, or created.Source: github.com
Which versions are affected by CVE-2026-86005?
chartbrew: before 5.2.3.Source: cve.now feed data
Am I affected, and how do I check?
Chartbrew versions before 5.2.3 are affected when Redis and BullMQ are enabled, the backend is network-accessible, and no reverse proxy independently blocks /apps/queues. To check, confirm the installed Chartbrew version, whether Redis and BullMQ are enabled in the deployment, and whether the proxy blocks that route.Source: github.com
How do I fix CVE-2026-86005?
Upgrade Chartbrew to 5.2.3 or later, which is the listed fixed version.Source: github.com