llamaCVEVulnerability Intelligence
/
Chartbrew

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.

Default setupsParche disponiblesignature verification bypass
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Fuente: CNA
ExplotaciónPoC públicaSSVC: poc · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión5.2.3
Exposición12 dDesde la divulgación, 6 nov 2026, 4:06 p. m.
Detección11 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Existe PoC pública, automatizable e impacto técnico parcial. Hay versiones corregidas disponibles.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC +1
Explotación
Remediación
Monitoreo
Detectada +1
Fuente: OSV
Verificada
6 nov 26
10 nov 26
16 nov 26
19 nov 26
6 nov 26
10 nov 26
13 nov 26
16 nov 26
19 nov 26
FechaFaseEventoDetalle
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
Resumen
Resumen generado por IA · CC-BY 4.0 · 6 nov 2026

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.

¿Qué significa?A forged share token signed with a known or default CB_SECRET can be accepted by the server. This lets someone without a valid share link read any private chart's data, including chartData, and expired or revoked tokens are not enforced.
¿Quién está afectado?Chartbrew server version 5.2.2 or earlier is affected, but only when the instance runs a known or default CB_SECRET, such as a source install or the repo docker compose setup, and the chart has been shared at least once. Check the server version and whether CB_SECRET was left at a default value.
¿Qué hacer?Upgrade the chartbrew/chartbrew server to 5.2.3 or later. Also replace any known or default CB_SECRET with a long, random value.
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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Installs running a known or default CB_SECRET, such as source installs or repo docker compose“Installs running a known or default CB_SECRET”
02
The chart has been shared at least once, so a share policy row exists“Any chart that has been shared once, so a share policy row exists”
03
Chartbrew server version 5.2.2 or earlier“chartbrew/chartbrew server, <= v5.2.2”
¿Quién debe revisar?Teams running chartbrew server 5.2.2 or earlier from source or the repo docker compose with the default or a known CB_SECRET, especially those sharing private charts
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:N
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
chartbrew< 5.2.3
5.2.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
chartbrew
Corregida 5.2.3 — —
Versiones corregidas5.2.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://github.com/chartbrew/chartbrew/security/advisories/GHSA-3chp-cr6f-hp63
Otrahttps://github.com/chartbrew/chartbrew/commit/07fff78db39e1c073a0301ac382c565268824e09
Otrahttps://github.com/chartbrew/chartbrew/releases/tag/v5.2.3

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.