# CVE-2026-114471: Insertion of Sensitive Information into Log File in hMailServer


- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-g5mm-pj68-xrm8

## What is CVE-2026-114471?

CVE-2026-114471 is a medium-severity vulnerability in Progressive Robot Ltd hMailServer, published on 21 Oct 2026. 

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-114471?


## How do I fix CVE-2026-114471?

No fix has been published for CVE-2026-114471 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-114471 being exploited?

There is no known exploitation of CVE-2026-114471 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114471 and fix it if it is affected.

What it is: CVE-2026-114471 is a medium-severity vulnerability in Progressive Robot Ltd hMailServer, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114471 in the wild and no public exploit code.

Affected product: Progressive Robot Ltd hMailServer. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114471/ (Markdown: https://insights.sbomify.com/CVE-2026-114471/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114471
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114471
- OSV: https://osv.dev/vulnerability/CVE-2026-114471

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114471/
Summaries are generated and may contain mistakes; the official description above is the record.