CVE-2026-40904: Chartbrew: Incorrect Access Control in dataset and dataRequest routes via team-scoped permission checks
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 datasetid, dataRequest id, and connectionid 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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40904?
CVE-2026-40904 is considered a critical vulnerability due to incorrect access control in Chartbrew that could allow unauthorized access to datasets.
How do I fix CVE-2026-40904?
To fix CVE-2026-40904, upgrade Chartbrew to version 5.0.0 or later to ensure correct access control implementation.
What versions of Chartbrew are affected by CVE-2026-40904?
CVE-2026-40904 affects Chartbrew versions prior to 5.0.0.
What are the implications of CVE-2026-40904 for users?
Users of Chartbrew with CVE-2026-40904 are at risk of unauthorized access to sensitive datasets and may experience data breaches.
Is CVE-2026-40904 publicly known?
Yes, CVE-2026-40904 is publicly disclosed and documented in security advisories related to Chartbrew.