Skip to main content
VulnerabilityPublished

CVE-2026-85708: chartbrew · Improper Verification of Cryptographic Signature

Affects chartbrewSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 5.2.3 soon.

Data as of 6 Nov 2026, 21:19 UTC

CVSS 3.1 base score
7.5High
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 3.17.5
Patch
Available – fixed in 5.2.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A: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 vulnerability is fixed. Deployments should ensure that CB_SECRET is unique and unpredictable to prevent token forgery. If using stock or default secrets, rotate the secret to a strong, unique value. No other mitigation is indicated by the vendor advisory.

Description

Chartbrew versions prior to 5.2.3 contain a vulnerability in the verification of cryptographic signatures for chart share and embed tokens. The tokens were signed using a secret (CB_SECRET) that could be a known or default value in stock installations. An attacker who knows this secret can forge valid share tokens to access private chart data without authentication by enumerating chart IDs. This vulnerability is fixed in version 5.2.3.

References

Community reviews

Loading reviews…