Skip to content
Connect AISign inSign up free
CVE-2026-1075777.5HighCWE-835

CVE-2026-107577: Loop with Unreachable Exit Condition ('Infinite Loop') in hMailServer

Progressive Robot Ltd · hMailServer

Vendor fix available · Affected: Progressive Robot Ltd hMailServer · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
37th percentile
050100

Higher than 37% of scored CVEs

7.5HighCVSS 3.1
LowHigh

DescriptionCVE.org

Inefficient algorithmic complexity and a non-terminating loop in the MIME processing of received messages in Progressive Robot hMailServer 6.0.0 through 6.3.5 allow a remote unauthenticated attacker to make the mail services unavailable by sending a message. Removing a MIME header parameter whose value is empty and directly followed by a semicolon (for example a Content-Disposition with 'filename=a.bat; filename=;') entered a loop that never terminates, holding a worker thread at full load until the server is restarted; this is reached when the attachment blocker renames a blocked attachment or a filename is set over the REST API. Separately, decoding a header field that holds many RFC 2047 encoded words of an encoding other than base64 or quoted-printable, removing a parameter with many RFC 2231 continuations, and deleting many header fields of one name each took time growing with the square of the message, on the small thread pools that serve IMAP, SMTP and POP3 connections, delivery and the REST API.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • Progressive Robot Ltd · hMailServerfrom 6.0.0 before 6.3.6

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-107577 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References