CVE-2026-54589
Chartbrew SSRF guard bypass in API data connection outbound policy
A logged-in attacker who can edit API connections can read internal IPv4 responses, including cloud metadata.
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:L/SA:L
Fuente: CNA
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | CVE-2026-54589 divulgada · CVSS 7 (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, contains an SSRF guard bypass in its API Data Connection outbound request policy that lets a remote attacker with high-privilege, logged-in access read responses from internal IPv4 hosts, including cloud metadata services, through a NAT64/DNS64 gateway. The bypass only works in NAT64/DNS64 deployments, and it requires the attacker to be able to create or edit API connections.
Affects Chartbrew deployments on NAT64/DNS64 networks where authenticated users can create or edit API data connections. Fixed in 5.2.1.
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.1, the outbound URL guard recognized ordinary IPv4, IPv6, and IPv4-mapped IPv6 destinations but did not recognize IPv4 addresses embedded in NAT64 prefixes. The vulnerable surface is aPI Data Connection outbound requests routed through server/modules/outboundTargetPolicy.js. An authenticated user with permission to create or edit an API connection supplies an attacker-controlled hostname or redirect whose DNS answer is a NAT64 address embedding a private or link-local IPv4 destination. The policy treated the NAT64 address as public; a NAT64 gateway then translated it to the embedded private IPv4 address after validation. The bypass requires a NAT64/DNS64 deployment path and connection-management privileges. IPv4-only deployments are not affected by this specific bypass. The attacker can read responses from 169.254.169.254 cloud metadata and arbitrary internal IPv4 hosts and ports reachable through the NAT64 gateway. This issue is fixed in version 5.2.1.
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.1 | — | — |
5.2.1Arsenal 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-6m7q-jmp7-3vw8https://github.com/chartbrew/chartbrew/commit/8cfac8076bb0001b1571d93ef923698f53767751https://github.com/chartbrew/chartbrew/releases/tag/v5.2.1Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
