Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-107574 Overview
CVE-2026-107574 is an algorithmic complexity vulnerability in the JSON reader of Progressive Robot hMailServer. The reader keeps the first of each duplicated member name by linearly searching previously parsed members, producing O(N^2) parsing cost for an object with N distinct member names. A 1 MB payload takes 8.9 seconds and a 4 MB payload takes 300 seconds against the affected code. A remote unauthenticated attacker can deliver a crafted TLS-RPT report (up to 16 MB after decompression) to a hosted domain's published report mailbox, exhausting delivery threads and halting mail flow.
Critical Impact
A small number of crafted TLS-RPT reports can hold every delivery thread (ten by default) for over an hour per report, blocking all local and outbound mail delivery.
Affected Products
- Progressive Robot hMailServer versions prior to 6.3.6
- Deployments with a configured TLS-RPT report mailbox for a hosted domain
- Webmail REST API endpoints accepting JSON bodies up to 16 MB (authenticated path)
Discovery Timeline
- 2026-10-08 - CVE-2026-107574 published to NVD
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-107574
Vulnerability Analysis
The flaw is an algorithmic complexity weakness [CWE-407] in the hMailServer JSON reader. When parsing a JSON object, the reader preserves the first value for each duplicated member name by searching through all previously parsed members for a match. This linear duplicate check runs on every new member, producing quadratic time complexity relative to the number of distinct members in the object.
The practical effect is severe for large JSON bodies. A 1 MB object takes approximately 8.9 seconds of CPU time, and a 4 MB object takes approximately 300 seconds. Because the parser executes synchronously on worker threads, a request holds the thread for the entire parse duration.
Root Cause
The JSON reader implements duplicate member handling using an O(N) linear scan of already-parsed members for each new member added to an object. Processing N members therefore costs O(N^2) comparisons. A hash-based or sorted lookup would reduce this to O(N log N) or O(N) and eliminate the complexity amplification.
Attack Vector
Two exploitation paths exist. The unauthenticated path targets the TLS-RPT reporting mailbox. An attacker emails a crafted TLS-RPT report, which decompresses to as much as 16 MB, to a hosted domain's published report address. The report is parsed on a delivery thread. A handful of such messages occupy all ten default delivery threads, stopping local and outbound mail for over an hour per report.
The authenticated path reaches the same 16 MB body through the webmail REST routes, consuming the REST API worker thread pool instead of delivery threads. Deployments without a configured report mailbox are not affected by the unauthenticated vector, because unauthenticated REST sign-in routes cap JSON bodies at 64 KB.
No verified public exploit code is available. See the GitLab hMailServer Work Item #76 for technical details of the root cause and fix.
Detection Methods for CVE-2026-107574
Indicators of Compromise
- Inbound email messages to the TLS-RPT report mailbox containing attachments that decompress to multi-megabyte JSON objects with many distinct keys.
- Prolonged mail delivery queue stalls lasting an hour or more with no apparent network or DNS fault.
- hMailServer delivery threads showing sustained CPU utilization while handling a single message.
Detection Strategies
- Monitor hMailServer delivery thread occupancy and correlate long-running threads with recently received TLS-RPT reports.
- Inspect inbound TLS-RPT submissions for unusually large decompressed JSON payloads or objects with abnormally high member counts.
- Track webmail REST API latency and worker thread saturation for authenticated endpoints that accept JSON bodies.
Monitoring Recommendations
- Enable queue depth and delivery latency alerting on the hMailServer mail transfer agent.
- Log and alert on JSON payloads exceeding a defined size threshold on inbound mail and REST endpoints.
- Review authentication logs for webmail accounts submitting repeated large JSON bodies to REST routes.
How to Mitigate CVE-2026-107574
Immediate Actions Required
- Upgrade hMailServer to version 6.3.6 or later, which contains the fix referenced in the hMailServer 6.3.6 release notes.
- If upgrade is not immediately possible, remove or unpublish the TLS-RPT report mailbox for hosted domains to eliminate the unauthenticated vector.
- Audit webmail account activity for abusive submissions to REST endpoints that accept JSON bodies.
Patch Information
The vendor has released hMailServer 6.3.6, which addresses the quadratic duplicate-member check in the JSON reader. The release and corresponding fix are tracked in the GitLab hMailServer Work Item #76.
Workarounds
- Unpublish or remove the TLS-RPT RUA mailbox for hosted domains until the server is patched.
- Place an upstream mail gateway or filter that rejects TLS-RPT reports exceeding a conservative size, well below the 16 MB post-decompression limit.
- Restrict access to the webmail REST API to trusted networks or require stricter rate limiting on JSON endpoints.
# Example: reject oversized TLS-RPT submissions at an upstream MTA (Postfix)
# Limit message size to 1 MB for the TLS-RPT reporting address
smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/tlsrpt_size_limit,
permit
# /etc/postfix/tlsrpt_size_limit
# tlsrpt@example.com REJECT TLS-RPT reports larger than policy limit
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

