CVE-2026-114471
Last modified
CVE-2026-114471 is a medium-severity vulnerability rated 4.7/10 on the CVSS scale. 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). EPSS estimates a 0.10% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Progressive Robot Ltd | hMailServer | >= 6.0.0, <= 6.3.6 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-114471?
How severe is CVE-2026-114471?
How do I fix CVE-2026-114471?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-11446The Booktics – Booking Calendar for Appointments and Service…5.3
- CVE-2026-114460A flaw was found in mod_qos. An off-by-one pointer calculati…5.3
- CVE-2026-114462Improper link resolution before file access ('link following…6
- CVE-2026-114463The webhook platform gateway in Nous Research Hermes Agent v…7.5
- CVE-2026-11447A security flaw has been discovered in GL.iNet GL-MT3000 up …6.3
- CVE-2026-114470Cross-site request forgery in the REST API of Progressive Ro…5.3
- CVE-2026-114472Insufficient resource pool in the ACME HTTP-01 challenge res…3.7
- CVE-2026-114473Incorrect authorization in the Sender Rewriting Scheme (SRS)…5
- CVE-2026-114474Use of a less trusted source for the envelope sender in the …5.9
- CVE-2026-114475Missing authorization in the REST role-management routes of …6.5
- CVE-2026-114476Incorrect authorization in the REST administration API of Pr…7.5
- CVE-2026-114477Missing authorization in the REST metrics route of Progressi…4.3
Are you affected by CVE-2026-114471?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
