dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-40904

HIGH · 8.1 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 →
87/100
Remediation priority · High
Remotely reachable 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 multiple dataset and dataRequest endpoints that authorize low-privileged project members at the team level instead of binding the requested dataset_id, dataRequest id, and connection_id to the caller's allowed projects. An authenticated attacker who only has access to one project inside a team can read, execute, create, update, and delete datasets and data requests that belong to other projects in the same team. The issue is exploitable remotely with ordinary project-level credentials and leads to cross-project data disclosure and unauthorized use of victim-side database or API connections. 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

Chartbrew version 4.9.0 contains a broken access control vulnerability where dataset and dataRequest endpoints authorize at the team level instead of validating that the requested dataset_id, dataRequest_id, or connection_id belongs to the caller's specific allowed project. This allows an authenticated user with access to any one project within a team to read, create, update, delete, and execute datasets and dataRequests belonging to other projects in the same team, leading to cross-project data disclosure and unauthorized use of database/API connections.

MitigationUpgrade to Chartbrew version 5.0.0 or later, which contains the patch for this access control issue.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Determine installed Chartbrew version
    Check the version file in the Chartbrew installation directory (usually version file in the root or package.json), or query the application API endpoint that returns version info if available
    Affected if Version is 4.9.0 or any version prior to 5.0.0 (the patched release)
  2. Verify multi-project team configuration
    Query the Chartbrew database or API to list projects associated with each team. Check if any team contains more than one project
    Affected if User belongs to a team that has multiple projects configured, creating the condition where cross-project access becomes possible
  3. Identify user project memberships
    Query the user-team-project associations in the database to determine which specific projects each user has access to within their team(s)
    Affected if A user has access to at least one project, and their team contains other projects they should not access
  4. Inspect dataset and dataRequest authorization logic
    Review the server-side code for dataset and dataRequest API endpoints. Check if the authorization logic validates resource ownership at the project level (should) versus team level (vulnerable)
    Affected if Code shows authorization checks only verify team membership without validating that the requested dataset_id, dataRequest_id, or connection_id belongs to the caller's specific allowed project

You are affected if Chartbrew version is 4.9.0 or earlier, you have teams with multiple projects, and the authorization logic only checks team-level access without validating project-level resource ownership for datasets and dataRequests.

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 Chartbrew version 5.0.0 or later, which contains the patch for this access control issue.

Recommended fix High confidence

5.0.0

  1. Backup your Chartbrew database and configuration files before attempting any upgrade
  2. Review the official Chartbrew upgrade documentation at the project GitHub repository
  3. Upgrade Chartbrew from version 4.9.0 to version 5.0.0 using your deployment method (Docker, npm, or manual installation)
  4. After upgrading, verify that the application starts successfully
  5. Test that project-level access controls now properly restrict dataset and dataRequest access to only the caller's authorized projects
  6. Confirm that low-privileged team members can no longer access datasets or dataRequests from projects they are not members of
Caveat Major version upgrades (4.x to 5.x) may include breaking changes; review the changelog for any required migration steps before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40904 — 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-40904 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