{"api_version":"1","generated_at":"2026-10-08T13:51:36+00:00","cve":"CVE-2026-107584","urls":{"html":"https://cve.report/CVE-2026-107584","api":"https://cve.report/api/cve/CVE-2026-107584.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-107584","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-107584"},"summary":{"title":"Not Failing Securely ('Failing Open') in hMailServer","description":"Progressive Robot hMailServer 6.0.0 through 6.3.5 fails open when applying DANE (RFC 7672) to outbound SMTP delivery. The server's validating DNSSEC resolver treated a TLSA or MX lookup that did not complete (no answer, SERVFAIL, a malformed reply), an answer without the requested records and without an NSEC/NSEC3 proof of their absence, and an answer whose records carried no applicable RRSIG as if the recipient domain were unsigned, and from 6.2.19 it also delivered to mail exchangers taken from an unvalidated MX lookup that the DNSSEC-validated MX record set did not name. An attacker who can drop, forge or strip DNS answers on the path to the server's resolver, at the resolver, or between the resolver and the recipient domain's name servers, and who holds an active position on the SMTP path, can thereby disable DANE for a DNSSEC-signed recipient domain and cause messages to be delivered in cleartext or to a host of the attacker's choosing with an arbitrary certificate, where they can be read and modified.","state":"PUBLISHED","assigner":"GitLab","published_at":"2026-10-08 12:17:16","updated_at":"2026-10-08 12:17:16"},"problem_types":["CWE-636","CWE-636 CWE-636: Not Failing Securely ('Failing Open')"],"metrics":[{"version":"3.1","source":"cve@gitlab.com","type":"Secondary","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":7.4,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"}},{"version":"3.1","source":"CNA","type":"CVSS","score":"7.4","severity":"HIGH","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","data":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}}],"references":[{"url":"https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6","name":"https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6","refsource":"cve@gitlab.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://gitlab.com/hmailserver/hmailserver/-/work_items/64","name":"https://gitlab.com/hmailserver/hmailserver/-/work_items/64","refsource":"cve@gitlab.com","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-107584","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-107584","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Progressive Robot Ltd","product":"hMailServer","version":"affected 6.0.0 6.3.6 semver","platforms":[]}],"timeline":[],"solutions":[{"source":"CNA","title":"","value":"Upgrade to hMailServer 6.3.6, which treats an incomplete, unsigned or unproven DNSSEC answer for a TLSA or MX lookup under a signed zone as indeterminate, does not use a mail exchanger whose lookup was indeterminate, defers the delivery when none is left, delivers only to mail exchangers named by a DNSSEC-validated MX record set, and (for a host whose DNS servers are IPv6 only) asks those IPv6 servers. Until then, for each recipient domain whose mail must be protected, an SMTP route that names its mail exchangers with the connection security 'STARTTLS (required)', with remote certificate verification on (VerifyRemoteSslCertificate=1), prevents delivery in cleartext or to another host for that domain; and the server's DNS resolver should be one reached over a trusted path, such as a validating resolver on the same host.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"Found in the hMailServer project's own security review (Progressive Robot Ltd)","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"hMailServer","repo":"https://gitlab.com/hmailserver/hmailserver","vendor":"Progressive Robot Ltd","versions":[{"lessThan":"6.3.6","status":"affected","version":"6.0.0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"finder","value":"Found in the hMailServer project's own security review (Progressive Robot Ltd)"}],"descriptions":[{"lang":"en","value":"Progressive Robot hMailServer 6.0.0 through 6.3.5 fails open when applying DANE (RFC 7672) to outbound SMTP delivery. The server's validating DNSSEC resolver treated a TLSA or MX lookup that did not complete (no answer, SERVFAIL, a malformed reply), an answer without the requested records and without an NSEC/NSEC3 proof of their absence, and an answer whose records carried no applicable RRSIG as if the recipient domain were unsigned, and from 6.2.19 it also delivered to mail exchangers taken from an unvalidated MX lookup that the DNSSEC-validated MX record set did not name. An attacker who can drop, forge or strip DNS answers on the path to the server's resolver, at the resolver, or between the resolver and the recipient domain's name servers, and who holds an active position on the SMTP path, can thereby disable DANE for a DNSSEC-signed recipient domain and cause messages to be delivered in cleartext or to a host of the attacker's choosing with an arbitrary certificate, where they can be read and modified."}],"metrics":[{"cvssV3_1":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":7.4,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-636","description":"CWE-636: Not Failing Securely ('Failing Open')","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-10-08T11:49:16.083Z","orgId":"ceab7361-8a18-47b1-92ba-4d7d25f6715a","shortName":"GitLab"},"references":[{"url":"https://gitlab.com/hmailserver/hmailserver/-/work_items/64"},{"url":"https://gitlab.com/hmailserver/hmailserver/-/releases/v6.3.6"}],"solutions":[{"lang":"en","value":"Upgrade to hMailServer 6.3.6, which treats an incomplete, unsigned or unproven DNSSEC answer for a TLSA or MX lookup under a signed zone as indeterminate, does not use a mail exchanger whose lookup was indeterminate, defers the delivery when none is left, delivers only to mail exchangers named by a DNSSEC-validated MX record set, and (for a host whose DNS servers are IPv6 only) asks those IPv6 servers. Until then, for each recipient domain whose mail must be protected, an SMTP route that names its mail exchangers with the connection security 'STARTTLS (required)', with remote certificate verification on (VerifyRemoteSslCertificate=1), prevents delivery in cleartext or to another host for that domain; and the server's DNS resolver should be one reached over a trusted path, such as a validating resolver on the same host."}],"title":"Not Failing Securely ('Failing Open') in hMailServer"}},"cveMetadata":{"assignerOrgId":"ceab7361-8a18-47b1-92ba-4d7d25f6715a","assignerShortName":"GitLab","cveId":"CVE-2026-107584","datePublished":"2026-10-08T11:49:16.083Z","dateReserved":"2026-10-08T10:52:25.635Z","dateUpdated":"2026-10-08T11:49:16.083Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-08 12:17:16","lastModifiedDate":"2026-10-08 12:17:16","problem_types":["CWE-636","CWE-636 CWE-636: Not Failing Securely ('Failing Open')"],"metrics":{"cvssMetricV31":[{"source":"cve@gitlab.com","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","baseScore":7.4,"baseSeverity":"HIGH","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE"},"exploitabilityScore":2.2,"impactScore":5.2}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"107584","Ordinal":"1","Title":"Not Failing Securely ('Failing Open') in hMailServer","CVE":"CVE-2026-107584","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"107584","Ordinal":"1","NoteData":"Progressive Robot hMailServer 6.0.0 through 6.3.5 fails open when applying DANE (RFC 7672) to outbound SMTP delivery. The server's validating DNSSEC resolver treated a TLSA or MX lookup that did not complete (no answer, SERVFAIL, a malformed reply), an answer without the requested records and without an NSEC/NSEC3 proof of their absence, and an answer whose records carried no applicable RRSIG as if the recipient domain were unsigned, and from 6.2.19 it also delivered to mail exchangers taken from an unvalidated MX lookup that the DNSSEC-validated MX record set did not name. An attacker who can drop, forge or strip DNS answers on the path to the server's resolver, at the resolver, or between the resolver and the recipient domain's name servers, and who holds an active position on the SMTP path, can thereby disable DANE for a DNSSEC-signed recipient domain and cause messages to be delivered in cleartext or to a host of the attacker's choosing with an arbitrary certificate, where they can be read and modified.","Type":"Description","Title":"Not Failing Securely ('Failing Open') in hMailServer"}]}}}