CVE-2026-107586
Allocation of Resources Without Limits or Throttling in hMailServer
02 Description
Allocation of Resources Without Limits or Throttling 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.33% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 26.9% of scored records. A rank, not a probability.
- NVD base score
- 4.3 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- 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 15:11Z21 DAYS AGO
- Last updated
- 2026-10-08 19:12Z20 DAYS AGO
- Reserved
- 2026-10-08
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 4.3)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- Weaknesses
- CWE-770Allocation of Resources Without Limits or ThrottlingBase
- Data version
- 5.2
- Document digest
- e1f147a96f2046ec03d89f32e36c1162b20e8c4e01ac34665a3f59ccb9f9f89c
05 Affected products
06 References
07 Remediation
Upgrade to hMailServer 6.3.6, in which each account or administrator holds at most fifty sessions and gives up its own least recently used one, and a full table makes room out of the sessions of whoever holds the most. Until then: limit the rate of POST /api/v1/session per client at a reverse proxy in front of the listener, and disable an account found signing in repeatedly (its sign-ins are in the application log and its device list).