llamaCVEVulnerability Intelligence
/
Chartbrew

CVE-2026-85295

Chartbrew account takeover via forged JWT session tokens

Attackers can forge session tokens and impersonate any user, bypassing passwords and two-factor authentication.

Default setupsParche disponiblesecurity flaw
Descargar PNG JSON
CVSS 3.1
9.8
Crítica
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión5.2.3
Exposición12 dDesde la divulgación, 6 nov 2026, 4:05 p. m.
Detección12 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCAtender
Priorizar en el próximo ciclo de cambios
Sin explotación conocida, automatizable e impacto técnico total. 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
9 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-85295 divulgada · CVSS 9.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 ninguna
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 web app for building charts from databases and APIs, is affected when its session tokens can be forged, which an attacker can do remotely without logging in when the CB_SECRET value is known, weak, or the shipped default, as in stock source or repository Docker Compose installs. Such an attacker can impersonate any user, bypassing their password and two-factor authentication, and use that user's Chartbrew privileges across the API and socket layer.

Affects Chartbrew server up to 5.2.2 installed from source or docker-compose with CB_SECRET left at its shipped default. Fixed in 5.2.3.

¿Qué significa?Chartbrew accepts JWTs signed with a secret that is publicly known when CB_SECRET is left at its default. A forged token gives a full session as any user ID, which allows reading, changing, and deleting that user's data while bypassing password and 2FA.
¿Quién está afectado?Chartbrew server up to v5.2.2 is affected when CB_SECRET is the shipped default change_to_random_string or another known or weak value. Stock source and repo docker-compose installs ship with this default, so check the CB_SECRET value in your .env file.
¿Qué hacer?Upgrade the Chartbrew server to 5.2.3 or later. Set CB_SECRET to a unique random value rather than the shipped default.
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, four authentication helpers accepted session tokens signed with CB_SECRET, including known, weak, or shipped-default values. The vulnerable surface is session JWT fallback in server/modules/verifyToken.js, verifyUser.js, getUserFromToken.js, and socketManager.js across the API and socket layer. A stock source or repository Docker Compose deployment retains a known, weak, or default CB_SECRET and an attacker submits a forged HS256 token decoding to a target user id. Knowing the symmetric secret lets the attacker create a token that the legacy verification fallback accepts as the target user without that user's password or two-factor authentication. The condition includes stock source and repository Docker Compose installs and any otherwise known or weak CB_SECRET; a bare container where CB_SECRET is undefined is not affected by this fallback path. A forged session impersonates the chosen user across the entire API and socket layer and exercises that user's Chartbrew privileges. This issue is fixed in version 5.2.3.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
CB_SECRET is left at the shipped default change_to_random_string or another known or weak value“CB_SECRET ships in .env-template as the fixed value change_to_random_string”
02
Stock source install or repo docker-compose install (Chartbrew server up to v5.2.2)“A stock source or docker-compose install therefore authenticates with a globally known secret.”
03
Installs whose CB_SECRET is the shipped default or otherwise known or weak“Installs whose CB_SECRET is the shipped default change_to_random_string or otherwise known/weak”
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:H
AltoBajoNinguno
DisponibilidadA:H
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-qvv4-r3q6-8797
Otrahttps://github.com/chartbrew/chartbrew/commit/da8c71f156aaa13fbc7ead15a4726740fef2b3c5
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.