Chartbrew Cross-Tenant Authorization Bypass Vulnerability
Chartbrew versions prior to 4.9.0 are vulnerable to a cross-tenant authorization bypass, allowing an authenticated attacker to access project data belonging to other teams.
Chartbrew, an open-source web application used for creating charts from databases and APIs, is vulnerable to a cross-tenant authorization bypass (CVE-2026-32252) in versions prior to 4.9.0. This vulnerability resides in the GET /team/:team_id/template/generate/:project_id endpoint. Specifically, the checkAccess function doesn’t await its promise and fails to validate if the project_id belongs to the specified team_id or the attacker’s team. This allows an authenticated attacker with template generation permissions in their own team to request and receive template model data for projects belonging to other teams. Upgrading to version 4.9.0 or later resolves this issue.
Attack Chain
- Attacker authenticates to a Chartbrew instance with valid credentials and template generation permissions within their own team.
- Attacker identifies a valid
team_idbelonging to a victim team. This could be done through enumeration of team IDs, social engineering, or other means. - Attacker identifies a valid
project_idbelonging to the victim team. This may require some level of prior knowledge or reconnaissance. - Attacker crafts a GET request to
/team/:victim_team_id/template/generate/:victim_project_id, replacing:victim_team_idand:victim_project_idwith the identified values. - The Chartbrew server receives the request and calls the
checkAccessfunction, but does not await the promise. - Due to the missing validation of the
project_idagainst theteam_idand the caller’s team, the authorization check is bypassed. - The server retrieves the template model data associated with the victim’s project.
- The server returns the victim’s project data to the attacker.
Impact
Successful exploitation of this vulnerability allows an attacker to gain unauthorized access to sensitive project data belonging to other teams within the Chartbrew application. This could include confidential database connection strings, API keys, data schemas, and other information that could be used to further compromise the victim’s systems or data. The number of affected organizations depends on the adoption rate of Chartbrew instances prior to version 4.9.0.
Recommendation
- Upgrade Chartbrew to version 4.9.0 or later to patch CVE-2026-32252.
- Implement the Sigma rule
Detect Chartbrew Template Generation Requestto identify potential exploitation attempts in web server logs. - Monitor web server logs for unusual requests to the
/team/*/template/generate/*endpoint using a WAF or similar tool.
Detection coverage 2
Detect Chartbrew Template Generation Request
mediumDetects requests to the Chartbrew template generation endpoint which is vulnerable to authorization bypass.
Detect Chartbrew Unauthenticated Template Generation Request
highDetects unauthenticated requests to the Chartbrew template generation endpoint which is vulnerable to authorization bypass.
Detection queries are kept inside the platform. Get full rules →