CVE-2026-85712
Chartbrew cross-tenant project takeover in project routes
A low-privilege user can take over other teams' projects to read, edit, expose, or delete them.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-85712 divulgada · CVSS 8.8 (CNA) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Fuente: NIST NVD | Registro visto por primera vez en NIST NVD | |
| Divulgación | Evaluación SSVC | CISA-ADP · explotación PoC pública | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Chartbrew, an open-source web app that builds charts from databases and APIs, has a flaw in its project routes that lets a logged-in user control projects belonging to other teams. Remotely, an attacker with a low-privilege account that is an owner or admin of their own team can move a victim's project into their team, gain full read and write access, make it public, remove its password protection, or delete it.
Chartbrew server 5.2.2 and earlier are affected, most relevant where default self-signup is enabled. Fixed in 5.2.3.
Descripción original del registro (GitHub_M)
Chartbrew is an open-source web application that can connect directly to databases and APIs and use the data to create charts. Prior to 5.2.3, the shared project permission check trusted a caller-controlled team_id and let the teamOwner/teamAdmin branch continue without confirming that the target project belonged to that team. The vulnerable surface is project routes and related authorization checks that accepted user-controlled project identifiers. An authenticated user who is an owner or admin of their own team submits a victim project id together with the attacker's own team_id in the request body; default self-signup grants the required role on the user's own team. Authorization is evaluated against the attacker-selected team instead of the target project's team, and the update path mass-assigns the request body without a project field allow-list. The attacker needs a valid Chartbrew account, an owner or admin role on their own team, and a victim project identifier; requests without the body team_id trick are rejected. The attacker can re-parent the victim project into their own team, gain full read and write access, expose it publicly, remove password protection, and cause the victim to lose it; the shared delete route also permits cross-tenant deletion. This issue is fixed in version 5.2.3.
Condiciones y alcance
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
chartbrew |
Corregida | 5.2.3 | — | — |
5.2.3Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/chartbrew/chartbrew/security/advisories/GHSA-6gv3-8wxh-6vfqhttps://github.com/chartbrew/chartbrew/commit/9db1e57c95014256ef0a7a8a4d60af6e7ade42a5https://github.com/chartbrew/chartbrew/releases/tag/v5.2.3Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
