1296 matches found
CVE-2026-104658
The Linux live-update apply helper hmailserver-update of Progressive Robot hMailServer 6.3.4 and 6.3.5 runs as root on a request file written by the unprivileged hmailserver service account, and took from that request the program used to verify an AppImage update's signature and the systemd unit ...
CVE-2026-103649
Missing network timeouts in the Linux builds of Progressive Robot hMailServer 6.3.0 through 6.3.5 allow a remote attacker to hold server threads indefinitely and so stop outbound mail delivery denial of service. The server set its socket timeouts in the form Windows takes, which Linux refuses, an...
CVE-2026-103647
Cross-site scripting in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote attacker who can send a user an encrypted message to run script in the webmail's origin with that user's session. When the webmail decrypted an S/MIME message from 6.3.2 or an OpenPGP message...
CVE-2026-103011
Heap-based buffer overflow in the legacy Blowfish encryption routine BlowFishEncryptor::Encode, called by EncryptToString in Progressive Robot hMailServer 6.0.0 through 6.3.5 allows an authenticated mailbox user to cause a denial of service service crash, and possibly other unspecified impact. In...
EUVD-2026-94838
Heap-based buffer overflow in the legacy Blowfish encryption routine BlowFishEncryptor::Encode, called by EncryptToString in Progressive Robot hMailServer 6.0.0 through 6.3.5 allows an authenticated mailbox user to cause a denial of service service crash, and possibly other unspecified impact. In...
CVE-2026-103011
Progressive Robot hMailServer versions 6.0.0 through 6.3.5 are vulnerable to a heap-based buffer overflow in the legacy Blowfish encryption routine (BlowFishEncryptor::Encode , called by EncryptToString ). The flaw occurs because the padding loop can write up to 7 zero bytes between 2 and 232 byt...
EUVD-2026-94837
Heap-based buffer overflow in the legacy Blowfish decryption routine BlowFishEncryptor::DecryptFromString in Progressive Robot hMailServer 6.0.0 through 6.3.3 on Windows allows a local interactive user with no hMailServer credentials to write bytes of their choosing past the end of a 255-byte hea...
EUVD-2026-94836
Cross-site scripting in the webmail of Progressive Robot hMailServer 6.3.2 through 6.3.5 allows a remote attacker who can send a user an encrypted message to run script in the webmail's origin with that user's session. When the webmail decrypted an S/MIME message from 6.3.2 or an OpenPGP message...
CVE-2026-103647
Progressive Robot hMailServer versions 6.3.2 through 6.3.5 are vulnerable to Cross-Site Scripting (XSS) in the webmail component. The root cause occurs when the webmail decrypts S/MIME (version 6.3.2) or OpenPGP (version 6.3.4) messages in a browser, offering decrypted attachments as blob URLs ba...
CVE-2026-103649
Linux builds of Progressive Robot hMailServer versions 6.3.0 through 6.3.5 are vulnerable to a denial of service (DoS) due to missing network timeouts. The root cause is that the server sets socket timeouts in a Windows-specific format which Linux rejects, causing HTTPS clients to read without a ...
EUVD-2026-94835
Missing network timeouts in the Linux builds of Progressive Robot hMailServer 6.3.0 through 6.3.5 allow a remote attacker to hold server threads indefinitely and so stop outbound mail delivery denial of service. The server set its socket timeouts in the form Windows takes, which Linux refuses, an...
CVE-2026-103649 Synchronous Access of Remote Resource without Timeout in hMailServer
Missing network timeouts in the Linux builds of Progressive Robot hMailServer 6.3.0 through 6.3.5 allow a remote attacker to hold server threads indefinitely and so stop outbound mail delivery denial of service. The server set its socket timeouts in the form Windows takes, which Linux refuses, an...
CVE-2026-104659 Origin Validation Error in hMailServer
Missing Host header validation and missing throttling of failed administrator sign-ins in the REST API listener of Progressive Robot hMailServer 6.0.0 through 6.3.5 allow a remote attacker to brute-force the server administrator's password through the administrator's own browser by DNS rebinding...
CVE-2026-104660
Progressive Robot hMailServer versions 6.0.0 through 6.3.5 (Windows) are vulnerable to a missing authorization flaw in its COM objects. The service registers COM classes without DCOM access or launch permissions and fails to use a security descriptor during CoInitializeSecurity, allowing local in...
CVE-2026-104660 Missing Authorization in hMailServer
Missing authorization on COM objects in Progressive Robot hMailServer 6.0.0 through 6.3.5 Windows only lets a local interactive user with no hMailServer credential read and write arbitrary files as the service account and queue mail as any sender. The service registers its COM classes with no DCO...
CVE-2026-104658
Progressive Robot hMailServer versions 6.3.4 and 6.3.5 are vulnerable to a privilege escalation flaw in the hmailserver-update helper. The helper runs as root but processes a request file written by the unprivileged hmailserver service account. It improperly uses the program path for AppImage sig...
CVE-2026-104704
Progressive Robot hMailServer versions 6.0.0 through 6.3.5 are vulnerable to a flaw where the server fails to enforce TLS for outbound SMTP delivery when DNSSEC-validated TLSA records lack a DANE-EE (usage 3) record. Instead of strictly adhering to RFC 7672, the server treats certain unusable rec...
EUVD-2026-94831
Progressive Robot hMailServer 6.0.0 through 6.3.5 does not enforce TLS for outbound SMTP delivery to a mail exchanger whose DNSSEC-validated TLSA records contain no DANE-EE usage 3 record, contrary to RFC 7672 section 2.2. The server used only DANE-EE records and treated a validated TLSA record s...
CVE-2026-104704 Cleartext Transmission of Sensitive Information in hMailServer
Progressive Robot hMailServer 6.0.0 through 6.3.5 does not enforce TLS for outbound SMTP delivery to a mail exchanger whose DNSSEC-validated TLSA records contain no DANE-EE usage 3 record, contrary to RFC 7672 section 2.2. The server used only DANE-EE records and treated a validated TLSA record s...