Inefficient algorithmic complexity in the inbound DKIM and ARC signature verification of Progressive Robot hMailServer 6.0.0 through 6.3.5 allows a remote unauthenticated attacker to make the mail services unavailable by sending a message. Building the canonical header and choosing the header fields named in a signature's h= tag took time growing with the square of the message's header: the 'simple' canonicalisation prepended each continuation line of a folded field to the lines already gathered, and both canonicalisations searched the gathered fields from the bottom for each h= name and erased the match from the middle of the list. A message whose header holds very many fields, or a field folded over very many lines, with a DKIM-Signature the attacker signs for a domain they control, keeps a worker thread busy for tens of seconds per signature; up to ten signatures are evaluated per message by each of the DKIM and DMARC tests, on the threads that serve delivery and SMTP.
CVE-2026-107576
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-08. A secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 49EG Risk 49/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.4%
- EPSS %ILE
- 35th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 8, 2026
Last Modified
October 8, 2026
Advisory Details (2)
Auto-updated Oct 8, 2026hMailServer 6.3.6 · hmailserver / hMailServer · GitLab
https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6Inbound DKIM and ARC verification: building the canonical header and choosing the h= fields took time quadratic in the message's header, per signature (6.0.0-6.3.5) (#73) · Issues · hmailserver / hMailServer · GitLab
https://gitlab.com/hmailserver/hmailserver/-/work_items/73Vendor Advisories for CVE-2026-107576(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 22:02 UTCEG score recompute
- 2026-10-09 22:01 UTCGHSA enrichment
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-09 09:40 UTCGHSA enrichment
- 2026-10-08 21:18 UTCGHSA enrichment
- 2026-10-08 15:23 UTCEG score recompute
- 2026-10-08 15:23 UTCGHSA enrichment
- 2026-10-08 14:49 UTCEG score recompute
- 2026-10-08 14:49 UTCGHSA enrichment
- 2026-10-08 12:26 UTCEG score recompute
- 2026-10-08 11:57 UTCEG score recompute
- 2026-10-08 11:56 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-107576?
When was CVE-2026-107576 disclosed?
Is CVE-2026-107576 actively exploited?
What is the CVSS score of CVE-2026-107576?
How do I remediate CVE-2026-107576?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-107576
Is Your Infrastructure Affected by CVE-2026-107576?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.