CVE-2026-85708
Chartbrew private chart data disclosure via forgeable share tokens
Remote attackers can read private charts by forging share tokens when CB_SECRET is known or left at its default.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-85708 divulgada · CVSS 7.5 (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 app for building charts from databases and APIs, has a flaw in how it verifies share tokens that lets an attacker read private chart data, including chart contents, without a legitimate share link, if the deployment's CB_SECRET is known or left at a shipped default. The attack can be carried out remotely without logging in by forging tokens for sequential chart IDs, but only for private charts that have been shared at least once.
Affects Chartbrew server 5.2.2 and earlier only when running a known or default CB_SECRET and a chart has been shared at least once. CVSS scores it High (7.5). 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, Chart share and embed tokens were signed with CB_SECRET, including known or shipped-default values in stock source and repository Docker Compose installs. The vulnerable surface is chart share-token verification and filter-access routes for private charts. An attacker who knows the deployment's CB_SECRET targets a private chart that has been shared at least once so a share-policy row exists, then forges a Chart-subject token for that chart id. The known signing key permits valid Chart tokens, and the filter-access path accepts sequential integer ids without requiring a legitimate share link; token expiry and revocation are ineffective once the secret is known. The condition requires a known or default secret and an existing share-policy row. A bare container where CB_SECRET is undefined is outside this path, and a unique secret excludes it only while the value remains unknown and unpredictable. An unauthenticated attacker can enumerate integer ids and read arbitrary private chart data, including chartData, without possessing a legitimate share link. 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-3chp-cr6f-hp63https://github.com/chartbrew/chartbrew/commit/07fff78db39e1c073a0301ac382c565268824e09https://github.com/chartbrew/chartbrew/releases/tag/v5.2.3Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
