llamaCVEVulnerability Intelligence
/
Progressive Robot hMailServer

CVE-2026-126611

Progressive Robot hMailServer credential theft via database connection certificate flaw

A local attacker who can impersonate the database server can steal its login password and read or alter traffic to it.

Specific setups onlyParche disponibleimproper certificate validation
Descargar PNG JSON
CVSS 3.1
7.0
Alta
CVSS:3.1/AV:L/AC:H/PR:L/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ón6.3.8
Exposición9 dDesde la divulgación, 11 nov 2026, 3:30 a. m.
Detección11 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir de cerca
Monitorear y programar la remediación
Sin explotación conocida, no 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 +2
Fuente: OSV
Verificada
11 nov 26
12 nov 26
17 nov 26
20 nov 26
11 nov 26
13 nov 26
15 nov 26
18 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-126611 divulgada · CVSS 7 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 11 nov 2026

Progressive Robot Ltd's hMailServer fails to verify the database server's certificate when it connects to a local MySQL or MariaDB database, but only under a non-default configuration. A local attacker with low privileges who can impersonate the database server, such as by listening on its port while it is stopped or restarting, can capture the database login password and read and modify traffic between hMailServer and the database.

¿Qué hacer?Upgrade hMailServer to version 6.3.8, which is the listed fixed version. Until you can upgrade, a workaround is to set TlsCaFile to a file holding only the CA that issues the database server's certificate, at a path that uses only ASCII characters.
Descripción original del registro (GitLab)

Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database, TlsMode=verify-full and no TlsCaFile, does not verify the database server's certificate's issuer or name when the connection is one that MariaDB Connector/C treats as local - Server= set to 127.0.0.1, ::1 or localhost (on Linux a Unix socket), to . on Windows (a named pipe), or to a comma-separated list of servers that holds such an element - which allows a local attacker who can stand in for the database server, for example by listening on its port while it is stopped or restarting, to receive the database sign-in, the password included, and to read and modify the traffic between hMailServer and its database. hMailServer applied verify-full by turning the client's certificate verification on without a CA file, but MariaDB Connector/C 3.4.1 and later, on a connection they treat as local and with no CA file, accept any certificate within its validity period that is self-signed or sent with its own root, for any name (Connector/C 3.4.2 to 3.4.10 also one whose issuer they cannot find), so the client accepted the certificate an impostor made, asked no proof of the password and allowed a switch to an authentication method that sends the password unhashed, while hmailserver --check-database said the certificate had been checked against the system's trust store and the application log that it had been checked. The Windows builds bundle Connector/C 3.4.9 (6.3.4 to 6.3.6) and 3.4.11 (6.3.7); on Linux the distribution's client is used, and Connector/C 3.3 and 3.4.0 and Oracle's MySQL client are not affected. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.

Contexto

Condiciones y alcance

MitigaciónSet TlsCaFile to a file holding only the CA that issues the database server's certificate, at a path in ASCII alone.
Vector CVSS 3.1

Desglose de métricas

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

Rangos afectados

Afectada Corregida
hMailServer≥ 6.3.4 ≤ 6.3.7
6.3.4
6.3.7
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
hMailServer
Corregida 6.3.8 — —
Versiones corregidas6.3.8
Explotación

Arsenal público

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

Registro
EscenarioGENERALGitLab
solutionUpgrade to hMailServer 6.3.8, which reads Server= as MariaDB Connector/C does and refuses TlsMode=verify-full with no TlsCaFile before connecting, with HM7535 in the error log, on a connection the client treats as local or a Server= list that holds one, and which says, on such a connection with a TlsCaFile, that the certificate's issuer was checked and not its name. Until then, set TlsCaFile to a file holding only the CA that issues the database server's certificate, at a path in ASCII alone; the client then checks the certificate's issuer on such a connection, though not its name. On these versions the --check-database settings line and the application log say the certificate was checked either way, so they do not show the difference.GitLab
Referencias
Otrahttps://gitlab.com/hmailserver/hmailserver/-/work_items/113
Otrahttps://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8

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