Skip to main content
Vulnerability Database/CVE-2026-114471

CVE-2026-114471: hMailServer SMTP Information Disclosure

CVE-2026-114471 is an information disclosure flaw in Progressive Robot hMailServer that exposes authentication credentials in log files. This post covers the technical details, affected versions, and steps to protect your system.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-114471 Overview

CVE-2026-114471 is an information disclosure vulnerability in the SMTP server of Progressive Robot hMailServer versions 6.0.0 through 6.3.6. The flaw causes the SMTP service to write authentication credentials to its log file during several SASL (Simple Authentication and Security Layer) exchanges. The server only redacts AUTH PLAIN credentials when sent in one exact form after EHLO. Any other form, including pre-EHLO submissions, OAuth 2.0 bearer tokens, SCRAM-SHA-256 client proofs, and GSSAPI authenticators, is written in clear. A local user with read access to the log, or any party given a copy, can recover credentials.

Critical Impact

Local users or anyone receiving a copy of the SMTP log can harvest plaintext passwords, OAuth bearer tokens, and SCRAM material that enables offline password guessing.

Affected Products

  • Progressive Robot hMailServer 6.0.0 through 6.3.6 (SMTP server component)
  • hMailServer 6.2.0+ for AUTH XOAUTH2, AUTH OAUTHBEARER, and SCRAM-SHA-256 exposure
  • hMailServer 6.3.2+ for GSSAPI authenticator exposure on Windows installations

Discovery Timeline

  • 2026-10-21 - CVE-2026-114471 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-114471

Vulnerability Analysis

The vulnerability is categorized as insertion of sensitive information into a log file [CWE-532]. With SMTP logging enabled, hMailServer writes the raw SASL exchange to disk as the client sent it. The server attempts to redact credentials for the AUTH PLAIN mechanism, but the redaction logic matches a single canonical form. A PLAIN password sent before EHLO or with extra whitespace bypasses the filter. Credentials for AUTH XOAUTH2, AUTH OAUTHBEARER, and SCRAM-SHA-256 were introduced in version 6.2.0 and were never covered by the redaction logic. GSSAPI tokens, added in 6.3.2, are also written in clear.

For SCRAM-SHA-256, the logged client proof combined with the logged salt and iteration count is sufficient to mount an offline brute-force attack against the user's password. OAuth 2.0 bearer tokens are directly reusable until expiry.

Root Cause

The SMTP logging component serializes SASL frames before authentication-aware masking is applied. The redaction routine was authored against a single AUTH PLAIN syntax and does not account for alternate SASL mechanisms, pre-EHLO submissions, or whitespace variations.

Attack Vector

Exploitation requires local access with permission to read the SMTP log, or possession of a copied log file (for example, from a backup or support bundle). On Windows installations prior to 6.3.6, the log folder was readable by every local user, lowering the bar for a non-privileged account on the mail server to recover credentials. SMTP logging is off by default.

No verified public exploit code or proof-of-concept is available. The exposure is realized through passive log inspection rather than active network interaction.

Detection Methods for CVE-2026-114471

Indicators of Compromise

  • SMTP log entries containing readable AUTH PLAIN payloads sent before an EHLO command, or with non-standard spacing around the Base64 token.
  • Log lines preserving AUTH XOAUTH2 or AUTH OAUTHBEARER Base64 blobs that decode to Bearer ya29. or similar OAuth 2.0 tokens.
  • Presence of SCRAM-SHA-256 client proof, salt, and iteration count triplets in the same log line or session.
  • Access to the hMailServer log directory by non-administrative local accounts on Windows hosts running versions prior to 6.3.6.

Detection Strategies

  • Audit the hMailServer log directory ACL on Windows and alert on reads by accounts outside the service and administrator groups.
  • Scan historical SMTP logs for Base64 patterns adjacent to AUTH PLAIN, AUTH XOAUTH2, AUTH OAUTHBEARER, SCRAM-SHA-256, and GSSAPI keywords.
  • Correlate log-folder access events with subsequent authentication anomalies on exposed mailboxes.

Monitoring Recommendations

  • Forward SMTP service logs to a central store with restricted access and short retention until the server is patched.
  • Monitor for file copy, archive, or backup activity targeting the hMailServer log directory.
  • Track authentication failures and new-location sign-ins for accounts whose credentials may have appeared in exported logs.

How to Mitigate CVE-2026-114471

Immediate Actions Required

  • Upgrade hMailServer to version 6.3.7 or later, which addresses the redaction gaps and corrects Windows log folder permissions.
  • Disable SMTP logging until the upgrade is applied if logs are not required for operations.
  • Rotate passwords, OAuth 2.0 bearer tokens, and SCRAM credentials for every account that has authenticated via SMTP while logging was enabled on an affected version.
  • Restrict NTFS permissions on the existing log directory so only the service account and administrators can read its contents.

Patch Information

Progressive Robot released hMailServer 6.3.7 to fix the issue. See the hMailServer 6.3.7 release notes and the upstream tracking item at hMailServer Work Item #95 for details.

Workarounds

  • Turn off SMTP logging in the hMailServer administration console for installations that cannot be upgraded immediately.
  • Harden the log directory with explicit deny ACLs for Users and Authenticated Users on Windows.
  • Scrub or securely delete archived SMTP logs that may contain plaintext credentials before sharing them with third parties or support.

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.