llamaCVEVulnerability Intelligence
/
Progressive Robot hMailServer

CVE-2026-126623

Progressive Robot hMailServer denial of service in JSON parser via hash collisions

A remote, unauthenticated attacker can halt mail delivery by sending a crafted JSON report, such as a TLS-RPT report.

Specific setups onlyParche disponibledenial of service
Descargar PNG JSON
CVSS 3.1
7.5
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:31 a. m.
Detección10 minDesde la divulgación hasta su ingreso al índice
Decisión SSVCSeguir
Remediar en la ventana regular de mantenimiento
Sin explotación conocida, 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 +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-126623 divulgada · CVSS 7.5 (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

A remote, unauthenticated attacker can make Progressive Robot hMailServer stop delivering mail and become unavailable by sending it a crafted JSON object, such as a TLS-RPT report to a hosted domain's report mailbox. The object's member names are chosen to collide in the JSON reader's hash set, so reading it takes time that grows with the square of the number of names, and delivery stops for as long as such reports keep arriving.

Affects hMailServer 6.3.6 and 6.3.7 on Windows and Linux, and only in some setups: a domain report mailbox, or the REST API with a public base URL. Fixed in 6.3.8.

¿Qué significa?The bug lets a sender cause a denial of service by tying up mail delivery threads or REST API worker threads. Mail delivery, the REST API and webmail can become unavailable, but no data is read or changed.
¿Quién está afectado?Versions 6.3.6 and 6.3.7 on Windows and Linux are affected. The mail path needs a domain's report mailbox set by an administrator, and the password-protected reply route needs the REST API turned on and a public base URL set for message links. To check the setup, confirm the installed version and whether any domain has a report mailbox or a REST API listener with a public base URL configured.
¿Qué hacer?Upgrade to hMailServer 6.3.8, which fixes the bug. The fix changes the JSON reader to keep an object's member names in an ordered set.
Descripción original del registro (GitLab)

Inefficient algorithmic complexity in the JSON reader of Progressive Robot hMailServer 6.3.6 and 6.3.7 allows a remote attacker to hold the server's mail delivery threads or its REST API's worker threads, making mail delivery, the REST API and the webmail unavailable. 6.3.6 fixed CVE-2026-107574, in which reading a JSON object searched the member names already read for each new name, by keeping the names in a hash set; the set uses the standard library's hash, which takes no secret, so member names chosen to fall in one bucket of it still cost time growing with the square of their number. Against the released reader, one such object of 16 MB took about 5 seconds to read in the Linux build, and one of under 6 MB about 23 seconds in the Windows build, where objects of the same sizes with other names took under a tenth of a second. A remote unauthenticated attacker reaches the reader by mailing such an object as a TLS-RPT report, up to 16 MB once decompressed, to a hosted domain's report mailbox, where an administrator has set one; it is read on a mail delivery thread (ten by default), and those threads deliver all mail, local and outbound, so a stream of such reports stops all delivery for as long as it continues. It is also reached without an account through the reply to a password-protected message, with the message's link alone, where the REST API is on (it is off by default) and a public base URL for such links is set; and by any account through the webmail's routes granted 16 MB, and by an application's API key through the send API. Each such request holds one of the REST API's four worker threads, in the process that also serves SMTP, IMAP and POP3.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
Affects hMailServer 6.3.6 and 6.3.7 on Windows and Linux.“6.3.6 and 6.3.7, on Windows and Linux: the hash set came in 6.3.6 (53e95b8326) and is unchanged in 6.3.7”
02
Mail path needs a domain's report mailbox set by an administrator.“where an administrator has set a domain's report mailbox”
03
Password-protected reply route needs the REST API on and a public base URL set for message links.“Links exist only where the REST listener is on and a public base URL for them is set”
¿Quién debe revisar?Anyone running hMailServer 6.3.6 or 6.3.7 on Windows or Linux, with a domain report mailbox set or the REST API enabled.
No protegeClearing the public base URL does not fix it.
MitigaciónClear each domain's report mailbox or move it off hosted domains; switch off OpenPGP in the webmail; limit who can reach the REST API or use a reverse proxy holding bodies well below 16 MB.
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:N
AltoBajoNinguno
IntegridadI:N
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Versiones

Rangos afectados

Afectada Corregida
hMailServer≥ 6.3.6 ≤ 6.3.7
6.3.6
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, whose JSON reader keeps an object's member names in an ordered set, whose cost does not depend on which names are chosen, and holds a REST request body and a mailed TLS-RPT report to 10,000 members in an object; the reply to a password-protected message is held to 2 MB. Until then, clear each domain's report mailbox, or move it off the domains the server hosts, so that no report is read by the server; and switch OpenPGP in the webmail off (portal_enabled under /api/v1/settings/openpgp), and off for any domain or account that holds openpgp_portal_enabled on, which refuses the reply to a password-protected message before its body is parsed; clearing the public base URL is not enough, since links already made stay usable. For the routes that take an account or an API key, only limiting who can reach the REST API avoids it (RestApiPort 0, the default, turns it off), or a reverse proxy in front of it that holds request bodies well below 16 MB. Restarting the service ends a busy thread.GitLab
Referencias
Otrahttps://gitlab.com/hmailserver/hmailserver/-/work_items/111
Otrahttps://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.8
recordhttps://www.cve.org/CVERecord?id=CVE-2026-107574

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