High severity · published Apr 30, 2026
CVE-2026-40595
Chartbrew: Incorrect Access Control in public chart and export routes via missing onReport and SharePolicy checks
7.5
CVSS
0.3%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.3% · higher than 20% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CH
chartbrew · chartbrew
= 4.9.0 · source: vendor
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-40595
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-40595
github.com
https://github.com/chartbrew/chartbrew/releases/tag/v5.0.0
github.com
https://github.com/chartbrew/chartbrew/security/advisories/GHSA-mq7q-6xh6-5649
More from chartbrew
9.8
CVE-2026-27005
Chartbrew: SQL injection in date-type variable handling (applyMysqlOrPostgresVariables)
9.6
CVE-2026-30232
Chartbrew has SSRF in API Data Connection - No IP Validation on User-Provided URLs
8.8
CVE-2026-25888
Chartbrew: Remote Code Execution (RCE) via Vulnerable API
8.1
CVE-2026-40600
Chartbrew: Incorrect Access Control in project share policy routes via unbound policy_id
8.1
CVE-2026-40904
Chartbrew: Incorrect Access Control in dataset and dataRequest routes via team-scoped permission checks
