llamaCVEVulnerability Intelligence
/
Progressive Robot hMailServer

CVE-2026-126610

Progressive Robot hMailServer man-in-the-middle risk in database certificate checks

An attacker who can intercept the database link can read and alter traffic without logging in or any user action.

UnclearSin parche publicadoimproper certificate validation
Descargar PNG JSON
CVSS 3.1
7.4
Alta
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Fuente: CNA
ExplotaciónSin evidenciaSSVC: none · no figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
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. No hay versión corregida: aplique mitigaciones.
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
16 nov 26
18 nov 26
20 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-126610 divulgada · CVSS 7.4 (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 does not load its configured CA certificate file when the file name contains non-ASCII characters, so with a MySQL or MariaDB database and certificate verification enabled, it does not check the database server's certificate against that CA. A remote attacker who can intercept the connection to the database server can read and modify traffic between hMailServer and its database, without logging in or any user action, though the attack is hard to carry out.

¿Qué significa?The advisory classifies this as improper certificate validation in hMailServer. The checked facts do not describe the exact behavior beyond that title.
¿Quién está afectado?hMailServer 6.3.4 through 6.3.7 is listed as affected, in the setup where MariaDB Connector/C 3.4.2 to 3.4.10 is the client in use. To check, compare your hMailServer version and your MariaDB Connector/C version against those ranges.
¿Qué hacer?The checked facts do not name a fixed version or vendor patch ids for this vulnerability. Check the vendor's advisory for the current fix status.
no-patchThe checked facts do not name a workaround. Limiting or reviewing the MariaDB Connector/C client setup in use is the only related step the facts point to, and they do not say it mitigates the issue.
disagreeThe description says the issue is local, but the CVSS vector lists the attack vector as network (AV:N). The sources disagree on how the issue can be reached, and the checked facts do not resolve which is correct.
Descripción original del registro (GitLab)

Progressive Robot hMailServer 6.3.4 through 6.3.7, with a MySQL or MariaDB database and TlsMode=verify-full, does not hand the database client the CA file that TlsCaFile names when the file's name contains a character outside ASCII on Linux, or above U+00FF on Windows, which allows an attacker who can intercept the connection to the database server to read and modify the traffic between hMailServer and its database, by presenting, with MariaDB Connector/C 3.4.2 to 3.4.10 as the client, a certificate from any authority, its own included, for any name, and otherwise a certificate for the database server's name issued by any certificate authority in the system's trust store. The server converted the name for the client with the C runtime's conversion in the C locale, which gives an empty string for such a name, and then set no CA file at all, without an error, while certificate verification stayed on, so the client - MariaDB Connector/C, bundled on Windows and the distribution's on Linux - verified the certificate of a database server over the network against the system's trust store instead of the configured CA; Connector/C 3.4.2 to 3.4.10 (bundled on Windows in 6.3.4 to 6.3.6) went further and, with no CA file, took a certificate within its dates whose issuer it could not find, for any name, with neither its chain nor its name checked and no password proof, when the server offered first a sign-in method that hashes the password, which an attacker in the middle chooses (MariaDB's CONC-853, fixed in Connector/C 3.4.11), and Connector/C 3.4 accepted from a MariaDB 11.4 or later server a certificate the store did not vouch for when that server proved it held the account's password; on a connection it treats as local (127.0.0.1, ::1, a Unix socket, a named pipe, and localhost on Windows), Connector/C 3.4.1 and later checked neither the certificate's issuer nor its name, so that a local attacker able to stand in for the database server could present any certificate within its dates of its own making. The settings line of hmailserver --check-database still named the configured file, and the application log said the certificate had been checked. With MariaDB Connector/C 3.4.1 to 3.4.9 as the client - bundled on Windows in 6.3.4 to 6.3.6, and the client of Linux distributions that have not patched it - the missing CA file also met the precondition of CVE-2026-107819, so that a certificate issued for any other name by a trusted authority was enough to obtain the database password. On Linux the file was found only when the server ran on glibc under a locale whose character set holds the name's characters (a UTF-8 locale, or a legacy 8-bit one the system has, in whose bytes the file is then named); with no locale, LC_ALL=C or a locale the system lacks, and on Alpine (musl), the connection failed instead. The configuration is not the default: TlsMode defaults to prefer, which checks no certificate.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
MariaDB Connector/C 3.4.2 to 3.4.10 is the client in use“with MariaDB Connector/C 3.4.2 to 3.4.10 as the client”
Discrepancias entre fuentesdescription-says-local-vector-says-AV:N
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:H
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:N
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
Sin parche — — —
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 hands the database client the CA file's name in the encoding the client opens it in - UTF-8 on Linux whatever the locale, the ANSI code page on Windows - and refuses before connecting, with HM7534 in the error log, a name it cannot write so, never handing over an empty one. Until then, give TlsCaFile a path in ASCII alone, which every affected version hands to the client as it is; on these versions the settings line of hmailserver --check-database names the configured file whether or not the client was given it, so it does not show the difference. On Linux, also update the distribution's MariaDB Connector/C to 3.4.11 or later, which fixes both CVE-2026-107819 and CONC-853, where one is offered; a version with the fix for CVE-2026-107819 alone still accepts a certificate whose issuer it cannot find.GitLab
Referencias
Otrahttps://gitlab.com/hmailserver/hmailserver/-/work_items/112
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.