01 Record
CVE-2026-107580
Inefficient Algorithmic Complexity in hMailServer
MediumPUBLISHEDCNA: GitLab
CNA base score6.5 CVSS v3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
02 Description
Inefficient Algorithmic Complexity in hMailServer
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.25% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 17.1% of scored records. A rank, not a probability.
- NVD base score
- 6.5 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- NVD analysis status
- Deferred. NVD last modified this record on 2026-10-08.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-08 11:47Z20 DAYS AGO
- Last updated
- 2026-10-08 14:20Z20 DAYS AGO
- Reserved
- 2026-10-08
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 6.5)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-407Inefficient Algorithmic ComplexityClass
- Data version
- 5.2
- Document digest
- 314ca6353108f80d537886c2017799ea3c61b9c7b37372ffe90e0fc37ac357a3
05 Affected products
VendorProductVersionsPlatforms
06 References
07 Remediation
Upgrade to hMailServer 6.3.6, which unfolds a header value in one pass and searches a header being read only in what each read adds. Until then: lower the maximum message size, which bounds the cost (it grows with the square of the value's size); remove such a message over POP3; or keep the REST listener off (RestApiPort 0, the default).