Cross-project dashboard disclosure via same-team authorization bypass
Published Apr 30, 2026 · Updated Apr 30, 2026
Improper access control in Chartbrew 4.9.0 allows remote authenticated users to read restricted dashboard data through a legacy API route. The /api/project/dashboard/:brewName handler accepts any same-team role, omits the project-membership check, and returns the raw project instead of its sanitized copy. Same-team membership and knowledge or guessing of brewName are required; exposure includes report content, share settings, and the stored report password.
Summary
What happened
Improper access control in Chartbrew 4.9.0 allows remote authenticated users to read restricted dashboard data through a legacy API route. The /api/project/dashboard/:brewName handler accepts any same-team role, omits the project-membership check, and returns the raw project instead of its sanitized copy. Same-team membership and knowledge or guessing of brewName are required; exposure includes report content, share settings, and the stored report password.
The record
- CVE
- CVE-2026-40603
- Published
- Apr 30, 2026
- Updated
- Apr 30, 2026
- Vendor
- Chartbrew
- Product
- Chartbrew
- Classifications
- CWE-284, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 2026CVE publishedPublication date reported by the CVE source.
- Apr 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 4.9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Vendor same-team dashboard disclosure PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo