Skip to main content
VulnerabilityPublished

CVE-2026-86005: chartbrew · Missing Authentication for Critical Functionality

Affects chartbrewSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 5.2.3 as a priority.

Data as of 6 Nov 2026, 21:19 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.09.3
Patch
Available – fixed in 5.2.3
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade chartbrew to 5.2.3.

Affected software

ProductAffectedFixed in
chartbrewchartbrewAffected
  • <5.2.3
Fixed in
  • 5.2.3

AI-suggested

Upgrade Chartbrew to version 5.2.3 or later, where this authentication bypass vulnerability is fixed. Until upgraded, ensure that the /apps/queues route is not reachable externally, for example by configuring reverse proxies or firewalls to block access to this path. Do not rely on network reachability as an authorization mechanism.

Description

Chartbrew versions prior to 5.2.3 expose the BullMQ administrative dashboard at /apps/queues without authentication. This allows remote unauthenticated attackers to access queue management functions if Redis and BullMQ are enabled and the route is reachable. Attackers can inspect job payloads and logs, and potentially retry, delete, or alter jobs, impacting confidentiality, integrity, and availability. The issue is fixed in version 5.2.3.

References

Community reviews

Loading reviews…