CVE-2026-107585
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.
- AutomatableyesAn attacker can reliably automate reconnaissance through exploitation, so this scales.
- Technical ImpactpartialSuccessful exploitation gives limited control of the vulnerable component.
- EPSS probability
- 0.44% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 38.6% of scored records. A rank, not a probability.
- NVD base score
- 5.3 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/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:11Z20 DAYS AGO
- Last updated
- 2026-10-08 19:13Z20 DAYS AGO
- Reserved
- 2026-10-08
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.3)
- CNA CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/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
- c6f5821f0541c036df4f0828f50304b4a61bfa33dca210263a62394c4df82b50
05 Affected products
06 References
07 Remediation
Upgrade to hMailServer 6.3.6, in which a pending OpenID Connect, SAML or passkey sign-in is no longer held on the server at all but carried by the browser in a cookie sealed with AES-256-GCM under a key held only in memory and good once, so there is no table a flood of unauthenticated starts can fill. Until then: limit the rate of /portal/oidc/start, /portal/saml/start and /api/v1/passkeys/challenge per client at a reverse proxy, and keep password sign-in available for administrators.