Insertion of sensitive information into a log file in the SMTP server of Progressive Robot hMailServer 6.0.0 through 6.3.6 allows a local user who can read the server's log, or anyone given a copy of it, to obtain credentials. With SMTP logging enabled, the server hid the credential of an AUTH PLAIN command only when it was sent after EHLO in one exact form, and wrote the rest of the SASL exchange as the client sent it: a PLAIN password sent before EHLO or with extra spacing, the OAuth 2.0 bearer token of AUTH XOAUTH2 and AUTH OAUTHBEARER (from 6.2.0), the SCRAM-SHA-256 client proof (from 6.2.0), which with the logged salt and iteration count allows offline password guessing, and the GSSAPI authenticator (from 6.3.2). SMTP logging is off by default; on Windows before 6.3.6 the log folder was readable by every local user.
Severity
CVSS 3.1
4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.10%(unchanged from 0.10% a week ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532Insertion of Sensitive Information into Log File
Show the promptExplain CVE-2026-114471 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-114471?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-114471?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-114471 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
progressive robot ltd:hmailserver
Versions
From the CNA's record in the CVE List.
Product
Affected
Progressive Robot Ltd hMailServer
from 6.0.0 through 6.3.6
Attack patterns (CAPEC)
CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.