CVE-2026-126621
validatingZero is analyzing and reversing it now.GHSA-2q54-5c4c-vg9w ↗EUVD-2026-123337 ↗
description
Windows hMailServer 6.0.0-B1 through 6.3.7 can resolve certain non-ASCII TLS-related file names to an unintended file. A local attacker able to place files or directories at that alternate path may cause attacker-controlled TLS material to be used, enabling unauthorized certificate-based access, storage-connection interception, key disclosure, or TLS service disruption. The risk depends on affected non-default configuration and writable adjacent filesystem locations.
Still under analysis: more detail becomes available as the pipeline runs.
mitigation
On Windows, change all hMailServer TLS, client-certificate, object-store, and ACME file paths to ASCII-only names, and prevent untrusted local users from creating files or directories near those paths. Disable unused client-certificate authentication, object-store TLS, and ACME features until the paths and permissions have been reviewed.
outcome
Run in progress: no artifact yet.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-11-11 08:36Zghsa: trigger signal, started the run
- 2026-11-11 08:36Zcve.org record for CVE-2026-126621
this entry in the feed
GET /api/v1/feed/CVE-2026-126621
{ "etk_id": "ETK-2026-4160", "cve_id": "CVE-2026-126621", "display_id": "CVE-2026-126621", "ghsa_id": "GHSA-2q54-5c4c-vg9w", "euvd_id": "EUVD-2026-123337", "status": "in_pipeline", "anchor_state": "anchored", "title": "TLS filename encoding confusion in hMailServer", "summary": "Windows hMailServer 6.0.0-B1 through 6.3.7 can resolve certain non-ASCII TLS-related file names to an unintended file. A local attacker able to place files or directories at that alternate path may cause attacker-controlled TLS material to be used, enabling unauthorized certificate-based access, storage-connection interception, key disclosure, or TLS service disruption. The risk depends on affected non-default configuration and writable adjacent filesystem locations.", "mitigation": "On Windows, change all hMailServer TLS, client-certificate, object-store, and ACME file paths to ASCII-only names, and prevent untrusted local users from creating files or directories near those paths. Disable unused client-certificate authentication, object-store TLS, and ACME features until the paths and permissions have been reviewed.", "vendor": "Progressive Robot Ltd", "product": "hMailServer", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 6.0.0-B1, <= 6.3.7" ], "ecosystem": null, "fixed_versions": [], "package_name": "hMailServer", "purl": null } ], "cwes": null, "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": null, "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": null, "t0_at": "2026-11-11T08:36:26.283000+00:00", "signals": { "trigger_signal": { "at": "2026-11-11T08:36:26.283000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-11-11T08:36:26.283000+00:00", "url": "https://github.com/advisories/GHSA-2q54-5c4c-vg9w" } } }
published 2026-11-11 11:07Z
last change 2026-11-11 11:17Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.