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, Chart share and embed tokens were signed with CB_SECRET, including known or shipped-default values in stock source and repository Docker Compose installs. The vulnerable surface is chart share-token verification and filter-access routes for private charts. An attacker who knows the deployment's CB_SECRET targets a private chart that has been shared at least once so a share-policy row exists, then forges a Chart-subject token for that chart id. The known signing key permits valid Chart tokens, and the filter-access path accepts sequential integer ids without requiring a legitimate share link; token expiry and revocation are ineffective once the secret is known. The condition requires a known or default secret and an existing share-policy row. A bare container where CB_SECRET is undefined is outside this path, and a unique secret excludes it only while the value remains unknown and unpredictable. An unauthenticated attacker can enumerate integer ids and read arbitrary private chart data, including chartData, without possessing a legitimate share link. This issue is fixed in version 5.2.3.
Published: 2026-11-06
Score: 7.5 High
EPSS: n/a
KEV: No
Impact: Sensitive data disclosure
Action: Apply Patch
AI Analysis

Impact

Chartbrew allows users to create charts from data sources and share them via tokens. A vulnerability in versions prior to 5.2.3 permits an attacker who knows the application's CB_SECRET to forge chart‑share tokens and bypass the share-token verification, enabling access to private charts that have been shared at least once. This leads to discovery of sensitive chart data such as chartData through unauthenticated requests, representing a disclosure of confidential information (CWE‑347).

Affected Systems

The flaw affects all installations of Chartbrew that have not upgraded to v5.2.3 and that use the default or a known CB_SECRET value, including stock Docker‑Compose images and source distributions. Private charts that have been shared create a share‑policy row that the attacker can target, and the filter‑access route accepts sequential numeric chart IDs without validating a legitimate share link. Any deployment where the secret is unchanged and shared charts exist is vulnerable.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity. Although the EPSS score is not available, the vulnerability can be exploited without authentication once the secret is known, and existing share‑policy rows enable enumeration of chart IDs. The flaw is not listed in CISA's KEV catalog, but the potential for data loss in applications that expose sensitive metrics makes it a critical concern for users who rely on Chartbrew for confidential visualizations.

Generated by OpenCVE AI on November 6, 2026 at 22:54 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Chartbrew v5.2.3 or later to apply the fixed share‑token signing logic.
  • Configure a unique, random CB_SECRET for each deployment and avoid using the default value bundled with the source or Docker images.
  • After rotating CB_SECRET, clear existing share‑policy entries or restart the application to invalidate any pre‑existing forged tokens.

Generated by OpenCVE AI on November 6, 2026 at 22:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 06 Nov 2026 23:00:00 +0000

Type Values Removed Values Added
First Time appeared Chartbrew
Chartbrew chartbrew
Vendors & Products Chartbrew
Chartbrew chartbrew

Fri, 06 Nov 2026 21:15:00 +0000

Type Values Removed Values Added
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, Chart share and embed tokens were signed with CB_SECRET, including known or shipped-default values in stock source and repository Docker Compose installs. The vulnerable surface is chart share-token verification and filter-access routes for private charts. An attacker who knows the deployment's CB_SECRET targets a private chart that has been shared at least once so a share-policy row exists, then forges a Chart-subject token for that chart id. The known signing key permits valid Chart tokens, and the filter-access path accepts sequential integer ids without requiring a legitimate share link; token expiry and revocation are ineffective once the secret is known. The condition requires a known or default secret and an existing share-policy row. A bare container where CB_SECRET is undefined is outside this path, and a unique secret excludes it only while the value remains unknown and unpredictable. An unauthenticated attacker can enumerate integer ids and read arbitrary private chart data, including chartData, without possessing a legitimate share link. This issue is fixed in version 5.2.3.
Title Chartbrew: Private chart data disclosure via forgeable CB_SECRET share tokens
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

Chartbrew Chartbrew
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-06T21:06:25.700Z

Reserved: 2026-09-04T14:45:10.647Z

Link: CVE-2026-85708

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-11-06T21:17:11.183

Modified: 2026-11-06T21:17:11.337

Link: CVE-2026-85708

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T23:00:11Z

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature