/

CVE-2026-40595

Severity:

HIGH RISK

(7.5)

Improper Access Control in Chartbrew Public Chart Retrieval

CVE-2026-40595

Deferred

Vulnerability type

Category:

Improper Access Control

CWE:

CWE-284

Impact:

Unauthorized Data Access / Information Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Chartbrew 4.9.0 exposes chart retrieval and export endpoints that only check project-level public status and a team export toggle, but do not verify per-chart sharing rules.

This allows an unauthenticated attacker who knows a chart identifier in a public project to read or export data for charts that were intentionally hidden from public reports.

Affected context

The vulnerability occurs in Chartbrew deployments that:

  • Run version 4.9.0 (or similarly affected versions with the same logic),
  • Have at least one project marked as public,
  • Use chart sharing/reporting features where some charts are meant to remain hidden or private.

In this context, the HTTP routes responsible for retrieving and exporting chart data validate that the project is public (and, for exports, that exporting is enabled at the team level) but do not enforce per-chart SharePolicy rules to confirm that a specific chart is allowed on a public report.

Exploit preconditions

  • Attack surface: Public HTTP endpoints for chart retrieval and export.
  • Required access: No authentication required; the attacker interacts as an anonymous user.
  • Knowledge required: A valid chart identifier associated with a project that is exposed as public.
  • Trigger point: Issuing a request to the public chart retrieval or export routes, passing the known chart identifier.
  • Why exploitation is possible: The authorization logic stops after validating project-level and team-level flags and does not check whether the requested chart is individually permitted for public access under its SharePolicy or report configuration.

Why this happens

The root cause is incomplete authorization checks on public-facing chart retrieval and export routes.

While the application correctly verifies coarse-grained conditions (such as whether a project is public and whether a team has enabled exports), it fails to apply fine-grained access control at the chart level.

This maps to CWE-284: Improper Access Control, where the software does not enforce or incorrectly enforces authorization on resources, allowing access to objects (hidden charts) that should be restricted according to more specific sharing policies.

Potential impact

  • Unauthorized reading of chart data that was deliberately excluded from public reports.
  • Exposure of sensitive business metrics, internal KPIs, or operational dashboards to anyone who can guess or obtain chart identifiers.
  • Leakage of indirectly sensitive information, such as data trends, infrastructure details, or customer usage statistics.
  • Violation of data handling policies or contractual obligations if charts contain regulated or confidential information.

General mitigation guidance

Effective mitigation focuses on enforcing consistent, least-privilege access control at every data-access boundary:

  • Apply fine-grained authorization checks on all chart retrieval and export routes, confirming that both the project and the specific chart are eligible for public access.
  • Centralize authorization logic so route handlers reuse a single, well-tested policy evaluation function rather than re-implementing checks per endpoint.
  • Treat chart identifiers and similar resource IDs as sensitive, and avoid assuming they are unguessable or secret; design access control around explicit policies instead of obscurity.
  • Default new charts and reports to the least-privileged visibility, requiring explicit opt-in for public exposure.
  • Provide administrators with clear configuration and UI indicators showing which charts are actually accessible publicly, helping reduce misconfigurations.

How teams detect issues like this

Organizations can detect similar access control flaws through:

  • Code review: Look for public or unauthenticated routes that only check project-level or team-level flags without verifying resource-level policies (e.g., a chart's SharePolicy or visibility field).
  • Static analysis / linters: Define rules that flag endpoints bypassing centralized authorization helpers or directly querying resources without accompanying permission checks.
  • Security testing: Use automated or manual tests to request hidden or non-public charts via public endpoints while varying project-level visibility; confirm that access is denied when chart-level policies should restrict it.
  • Logging and monitoring: Instrument access logs with chart identifiers, project visibility flags, and user identity (or anonymous markers), then alert on anonymous access to resources flagged as non-public.

Sources

SourceLink
github.comgithub.com/chartbrew/chartbrew/releases/tag/v5.0.0
github.comgithub.com/chartbrew/chartbrew/security/advisories/GHSA-mq7q-6xh6-5649

Frequently asked

questions

Yes. The affected routes are exposed over HTTP, and an attacker can exploit them remotely as an unauthenticated user, provided they know or can obtain valid chart identifiers for a public project.

No. The issue arises specifically because the public routes do not require authentication beyond checking project-level public status and a team export toggle, so no user account or role is needed.

The safest approach is to centralize authorization decisions and apply them uniformly to all chart data access paths. Every retrieval or export of chart data should verify both the project's visibility and the chart's own SharePolicy or equivalent sharing configuration before returning any data.

Preventive strategies include using a standardized authorization layer for all protected resources, designing APIs so that resource access always flows through this layer, enforcing least-privilege defaults, and incorporating security-focused code review and automated tests that explicitly exercise access control boundaries for different resource types and visibility states.

Find out what's already
exploitable in your codebase.