dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-40595

HIGH · 7.5 CVSS v3.1 Published 2026-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. In version 4.9.0, Chartbrew exposes public chart retrieval and export routes that only verify project-level public access and, for exports, a team-level export toggle. The routes do not verify whether the target chart is actually allowed on the public report or whether the governing SharePolicy permits public access. An unauthenticated attacker who knows a chart identifier in a public project can read or export chart data for charts that were intentionally hidden from the report. This issue has been patched in version 5.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Chartbrew 4.9.0 where public chart retrieval and export routes only verify project-level public access and team-level export toggles, but fail to check whether individual charts are actually permitted on public reports or if SharePolicy allows public access. An unauthenticated attacker who knows a chart ID within a public project can read or export data from charts intentionally hidden from public reports.

MitigationUpgrade to version 5.0.0 which contains the patch, or implement application-level authorization checks that verify chart-level report permissions and SharePolicy rules before returning data on public routes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Chartbrew version
    Check the installed Chartbrew version by examining package.json, a version file, or the application metadata. If using Docker, check the image tag or build information.
    Affected if The installed version is 4.9.0 exactly or falls within the 4.x range prior to 5.0.0
  2. Verify public project access is enabled
    Examine the Chartbrew application configuration or database to determine if any projects have public access enabled. Look for project settings that allow unauthenticated access or public viewing.
    Affected if At least one project has public access enabled, creating potential entry points for unauthenticated requests
  3. Identify charts hidden from public reports
    Review individual chart configurations within publicly accessible projects. Check each chart's settings for permissions related to public reports or public sharing visibility.
    Affected if Any chart within a public project is configured to be hidden or restricted from public reports but exists in a project with public access enabled
  4. Inspect SharePolicy configuration
    Examine the SharePolicy rules or access control settings for charts. Determine whether SharePolicy is properly enforcing chart-level public access restrictions.
    Affected if SharePolicy is not properly configured or is missing checks to enforce chart-level restrictions on public routes

If running Chartbrew 4.9.0 or any 4.x version before 5.0.0 with public project access enabled and charts that should be restricted from public access, the IDOR vulnerability is likely present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 5.0.0 which contains the patch, or implement application-level authorization checks that verify chart-level report permissions and SharePolicy rules before returning data on public routes.

Recommended fix Moderate confidence

5.0.0

  1. Backup your current Chartbrew deployment and database before upgrading
  2. Upgrade Chartbrew from version 4.9.0 to version 5.0.0 using your deployment method (e.g., Docker, npm, or manual installation)
  3. After upgrading, verify that the application starts successfully and all services are running
  4. Test that public report functionality now correctly enforces chart-level access controls - confirm that charts intentionally hidden from public reports cannot be accessed by unauthenticated users
  5. Review the SharePolicy configuration for each project to ensure charts are properly configured for public access
Caveat Unknown - no breaking change information provided in the advisory; review Chartbrew 5.0.0 release notes for any migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40595 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data