dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-40601

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 POST /api/chart/:chart_id/query without authentication. The endpoint only checks team.allowReportRefresh and does not verify that the target chart belongs to a public report, that the project is public, or that sharing policy allows the operation. An unauthenticated attacker who knows a chart identifier can trigger a data refresh and retrieve the current data of private charts. 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 4.9.0 exposes POST /api/chart/:chart_id/query without authentication. The endpoint only checks team.allowReportRefresh but fails to verify the chart belongs to a public report, the project is public, or sharing policy permits the operation. An unauthenticated attacker with a chart ID can refresh and exfiltrate data from private charts.

MitigationUpgrade to Chartbrew version 5.0.0 or later which includes proper authentication and authorization validation for the endpoint.

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 installation and version
    Locate the Chartbrew installation and check its version. For npm installations: check package.json or run `npm list chartbrew`. For Docker: check the image tag. For deployed instances: access the application or check configuration files for version information.
    Affected if Version is 4.9.0 exactly or falls within the 4.x range before 5.0.0
  2. Verify the /api/chart/:chart_id/query endpoint is accessible
    Send a POST request to the endpoint with a valid chart ID but without any authentication credentials. Example: `curl -X POST https://your-chartbrew-server/api/chart/CHART_ID/query` with no Authorization header.
    Affected if The endpoint returns a 200 or any data response instead of requiring authentication (401/403)
  3. Check team.allowReportRefresh configuration
    If you have admin access, inspect the team settings or database records for the `allowReportRefresh` flag. This setting is checked by the vulnerable endpoint but is insufficient for proper security.
    Affected if allowReportRefresh is enabled (true) on teams that own the charts being queried
  4. Determine if charts are in public reports or public projects
    Review the chart and project configurations. Check if the chart belongs to a report marked as public, or if the parent project has public sharing enabled.
    Affected if Charts are in private reports, private projects, or have no explicit sharing policy defined, yet the query endpoint remains accessible without auth

A user is affected if running Chartbrew version 4.9.0 (or any 4.x version before 5.0.0) and the /api/chart/:chart_id/query endpoint accepts unauthenticated requests, regardless of whether the underlying report or project is intended to be private.

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 includes proper authentication and authorization validation for the endpoint.

Recommended fix High confidence

5.0.0

  1. Backup your current Chartbrew installation and database
  2. Review the Chartbrew 5.0.0 release notes for any breaking changes or migration requirements
  3. Stop the running Chartbrew service
  4. Update Chartbrew to version 5.0.0 (e.g., via npm install [email protected] or by pulling the new container image)
  5. Run any database migrations if required by the 5.0.0 release
  6. Verify the /api/chart/:chart_id/query endpoint now properly enforces authorization
  7. Restart the Chartbrew service
  8. Test that unauthenticated requests to the query endpoint are rejected for private charts
Caveat Version 5.0.0 is a major version upgrade from 4.9.0; review release notes for breaking changes before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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