CVE-2026-126621

waiting for further signalsZero needs more public information before it can validate it.

GHSA-2q54-5c4c-vg9w ↗EUVD-2026-123337 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Progressive Robot Ltd hMailServer >= 6.0.0-B1, <= 6.3.7
ETK-2026-4160Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 20msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h07m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

hMailServer 6.0.0-B1 through 6.3.7 on Windows can load unintended TLS-related files when configured paths contain certain non-ASCII names. A local attacker able to create a conflicting path may cause untrusted certificate authorities to be accepted, intercept object-store traffic, obtain ACME-managed private keys, or prevent TLS listeners from starting. Default configurations are not affected; exposure requires affected TLS file paths and, for some impacts, optional client-certificate, object-store, or ACME features.

mitigation

Upgrade Windows installations to hMailServer 6.3.8. Until upgraded, use ASCII-only TLS-related file paths, restrict write access near those paths, and disable optional client-certificate, object-store, and ACME features where not required.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 08:36Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 08:36Z
    ghsa: trigger signal, started the run
  2. 2026-11-11 08:36Z

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": "published",
  "anchor_state": "anchored",
  "title": "TLS file path confusion in hMailServer",
  "summary": "hMailServer 6.0.0-B1 through 6.3.7 on Windows can load unintended TLS-related files when configured paths contain certain non-ASCII names. A local attacker able to create a conflicting path may cause untrusted certificate authorities to be accepted, intercept object-store traffic, obtain ACME-managed private keys, or prevent TLS listeners from starting. Default configurations are not affected; exposure requires affected TLS file paths and, for some impacts, optional client-certificate, object-store, or ACME features.",
  "mitigation": "Upgrade Windows installations to hMailServer 6.3.8. Until upgraded, use ASCII-only TLS-related file paths, restrict write access near those paths, and disable optional client-certificate, object-store, and ACME features where not required.",
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.64627573333333,
  "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 12:45Z

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.