CVE-2026-107581
MEDIUMDescription
Progressive Robot hMailServer 6.0.0 through 6.3.5 processes several IMAP commands from a signed-in account in time quadratic in the command's length or in the number of elements it names, and can be made to hold memory out of proportion to a command. The FETCH data-item parser normalised a BODY[] section with a case-insensitive string replacement that copied the whole item per occurrence and split the item list by repeatedly copying the remainder of the command; the server's case-insensitive search compared a needle afresh at every position, so a long SEARCH TEXT key over a message cost the product of the two lengths; SEARCH message sets and the saved-result marker ($), SORT criteria, HEADER.FIELDS name lists and UID ranges were each read once per message rather than once per command; and a FETCH naming a message's sections very many times read and held every section in memory before sending any. An IMAP command may continue past one line through non-synchronizing literals, so one command can reach about eleven megabytes. The IMAP worker threads are a small pool shared with SMTP and POP3, so a signed-in user sending such commands can make the IMAP, SMTP and POP3 services stop responding (CWE-407) and can consume excessive memory (CWE-400).
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 15% of all known CVEs.
References
Related Vulnerabilities
Other CWE-407 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-27223 | Medium | 5.2 | 78% | - | Fix |
| CVE-2022-36021 | Medium | 5.5 | 60% | - | Fix |
| CVE-2021-33582 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-43485 | High | 7.5 | 3.1% | - | Fix |
| CVE-2024-43484 | High | 7.5 | 3.0% | - | Fix |
| CVE-2016-10396 | High | 7.5 | 2.9% | - | - |
Common questions
How do I fix CVE-2026-107581?
No published fix for CVE-2026-107581 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-107581 being actively exploited?
Not that we know of. CVE-2026-107581 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.25% is the estimated probability that it will be exploited in the next 30 days. That is higher than 15% of all scored CVEs.
How severe is CVE-2026-107581?
CVE-2026-107581 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-107581
Markdown
[](https://tridentstack.com/cve/CVE-2026-107581)HTML
<a href="https://tridentstack.com/cve/CVE-2026-107581"><img src="https://tridentstack.com/cve/badge/CVE-2026-107581.svg" alt="CVE-2026-107581"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-10-08.