CVE-2026-107578
Improper Link Resolution Before File Access ('Link Following') in hMailServer
02 Description
Improper Link Resolution Before File Access ('Link Following') in hMailServer
03 Exploitation and scoring
- Exploitation
- Assessed, none found. CISA's assessment recorded neither public exploit code nor evidence of exploitation when it was made.
- SSVC decision
- ExploitationnoneCISA recorded no public exploit code and no evidence of exploitation.
- AutomatablenoAt least one step from reconnaissance to exploitation cannot be reliably automated.
- Technical ImpacttotalSuccessful exploitation gives total control of the vulnerable component.
- EPSS probability
- 0.07% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 0.0% of scored records. A rank, not a probability.
- NVD base score
- 6.7 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
- NVD analysis status
- Deferred. NVD last modified this record on 2026-10-08.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2026-10-08 11:47Z21 DAYS AGO
- Last updated
- 2026-10-08 14:17Z21 DAYS AGO
- Reserved
- 2026-10-08
- Assigning CNA
- GitLab
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 6.7)
- CNA CVSS vector
- CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
- Weaknesses
- CWE-59Improper Link Resolution Before File Access ('Link Following')Base
- Data version
- 5.2
- Document digest
- 2411b41e0110e91ddc1d31f02fcc70707da9f6eb33da41db5005bde16fe942d7
05 Affected products
06 References
07 Remediation
Upgrade to hMailServer 6.3.6, in which every administrative command writes nothing to the logs and arms no crash recorder, writes the certificate only through folders held open and checked from the drive's root, reaches no file a database row names outside the data folder, and walks the data folder before any store command - going through a junction or mount point only when the administrators alone own and control it and refusing any other; and on Linux a store or object-storage command run as root first drops to the service account, so it follows no link that account planted. Until then: on Windows run the service as LocalSystem, or stop the service and check the program folder's Logs, Data, Temp and Database folders for junctions, mount points and symbolic links and that no message row names a path outside the data folder; on Linux run the store commands only as the service user, never as root.