Skip to main content

hMailServer CVE-2026-107572

| EUVDEUVD-2026-94856 MEDIUM
Inefficient Regular Expression Complexity (ReDoS) (CWE-1333)
2026-10-08 GitLab GHSA-cqgg-3g6j-wqjp
6.5
CVSS 3.1 · Vendor: GitLab
Share

Severity by source

Vendor (GitLab) PRIMARY
6.5 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
6.5 MEDIUM

Network-reachable Sieve requires a valid account (PR:L) with no interaction and low complexity; impact is availability-only server-wide delivery halt (A:H, C:N/I:N), scope unchanged within the mail service.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Analysis Generated
Oct 08, 2026 - 15:06 vuln.today
Patch available
Oct 08, 2026 - 13:31 EUVD

DescriptionCVE.org

Inefficient complexity in the Sieve filter evaluation of Progressive Robot hMailServer 6.2.24 through 6.3.5 allows an authenticated account holder to make the mail services unavailable with their own filter. A ':matches' pattern was matched by a backtracking descent whose time grew with the matched value's length raised to the number of wildcards, so a pattern such as '*a*a*a*b' over 800 characters took 44 seconds; and 'deleteheader' erased the fields it removed one at a time, so removing many fields of one name over a message's header cost O(N^2) (80,000 fields took 18.8 seconds). Sieve filters run on the small, shared delivery thread pool, so an account holder whose active script does this, fed a few messages they can send themselves, empties the pool and stops delivery for the whole server. The script is the account holder's own and cannot be set for another user.

AnalysisAI

Authenticated denial of service in Progressive Robot hMailServer 6.2.24 through 6.3.5 lets any account holder who can publish an active Sieve script exhaust the server's shared delivery thread pool using their own filters. A ':matches' pattern with several wildcards evaluated against a long string, or a 'deleteheader' rule that strips many same-named fields, consumes seconds of CPU per message (44 seconds for an '*a*a*a*b' pattern over 800 characters; 18.8 seconds to remove 80,000 header fields), and a handful of self-delivered messages is enough to stall mail delivery for every user on the instance. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

No credit card · 7-day full trial

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Requires a valid, authenticated hMailServer account (PR:L) on a server where user-defined Sieve filtering is enabled and active for that account. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment This is a genuine but moderate-priority denial-of-service issue, not a high-impact remote code execution risk. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Vendor-released patch: upgrade hMailServer to 6.3.6 or later, which addresses both the wildcard backtracking cost in ':matches' evaluation and the quadratic 'deleteheader' removal path; the fix is published at https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6 and described in the upstream work item https://gitlab.com/hmailserver/hmailserver/-/work_items/75. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

CVE-2026-100741 CRITICAL POC
9.8 Sep 27

Arbitrary JScript execution in Progressive Robot Ltd's hMailServer 6.0.0 through 6.3.3 on Windows lets an unauthenticate

CVE-2026-103647 HIGH
8.0 Oct 08

Cross-site scripting in Progressive Robot hMailServer 6.3.2 through 6.3.5 can let a remote, unauthenticated attacker exe

CVE-2026-107573 HIGH
7.8 Oct 08

Incorrect default permissions in the Windows installer for Progressive Robot hMailServer 6.0.0 through 6.3.5 let any loc

CVE-2026-103010 HIGH
7.8 Oct 08

Heap-based buffer overflow in hMailServer 6.0.0 through 6.3.3 on Windows lets a local interactive user - with no hMailSe

CVE-2026-104660 HIGH
7.8 Oct 08

Local privilege escalation in hMailServer 6.0.0 through 6.3.5 on Windows allows an authenticated local user-one with an

CVE-2026-104658 HIGH
7.8 Oct 08

Local privilege escalation in Progressive Robot hMailServer 6.3.4 and 6.3.5 on Linux allows an attacker who already has

CVE-2026-107579 HIGH
7.5 Oct 08

Denial of service in Progressive Robot hMailServer 6.3.4 and 6.3.5 lets a remote unauthenticated attacker stall mail del

CVE-2026-107576 HIGH
7.5 Oct 08

Denial of service in Progressive Robot hMailServer 6.0.0 through 6.3.5 lets a remote unauthenticated attacker stall mail

CVE-2026-107577 HIGH
7.5 Oct 08

Denial of service in Progressive Robot hMailServer 6.0.0 through 6.3.5 allows a remote unauthenticated attacker to make

CVE-2026-107574 HIGH
7.5 Oct 08

Denial of service in hMailServer arises from quadratic-time parsing of JSON objects: the reader preserved the first inst

CVE-2026-103649 HIGH
7.5 Oct 08

Unauthenticated network-based denial of service in the Linux builds of Progressive Robot hMailServer 6.3.0 through 6.3.5

CVE-2026-104659 HIGH
7.5 Oct 08

DNS rebinding against Progressive Robot hMailServer 6.0.0 through 6.3.5 allows a remote, unauthenticated attacker to bru

Share

CVE-2026-107572 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy