CVE-2026-107574
validatedZero produced an exploit or a check.GHSA-2c7f-jhwj-7q7h ↗EUVD-2026-94854 ↗
description
hMailServer contains inefficient JSON parsing that can consume worker threads and interrupt mail delivery or REST service. An unauthenticated attacker can trigger the mail-service impact by sending a malicious TLS-RPT report when a hosted domain has a configured report mailbox; authenticated webmail users can also reach the affected parser.
mitigation
Upgrade hMailServer to version 6.3.6. Until upgrading, reduce exposure by removing or disabling configured TLS-RPT report mailboxes where operationally feasible.
fixed in 6.3.6
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-08 11:46Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-107574
{ "etk_id": "ETK-2026-1277", "cve_id": "CVE-2026-107574", "display_id": "CVE-2026-107574", "ghsa_id": "GHSA-2c7f-jhwj-7q7h", "euvd_id": "EUVD-2026-94854", "status": "published", "anchor_state": "anchored", "title": "Quadratic JSON parsing denial of service in hMailServer", "summary": "hMailServer contains inefficient JSON parsing that can consume worker threads and interrupt mail delivery or REST service. An unauthenticated attacker can trigger the mail-service impact by sending a malicious TLS-RPT report when a hosted domain has a configured report mailbox; authenticated webmail users can also reach the affected parser.", "mitigation": "Upgrade hMailServer to version 6.3.6. Until upgrading, reduce exposure by removing or disabling configured TLS-RPT report mailboxes where operationally feasible.", "vendor": "Progressive Robot Ltd", "product": "hMailServer", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 6.2.28, < 6.3.6" ], "ecosystem": null, "fixed_versions": [ "6.3.6" ], "package_name": "hMailServer", "purl": null } ], "cwes": [ 407 ], "cvss_score": 7.5, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "epss_score": 0.0043, "epss_percentile": 0.357, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 40.93474211666667, "t0_at": "2026-10-08T11:46:26.206000+00:00", "signals": { "check": { "at": "2026-10-12T02:18:07.585394+00:00", "days": 3.6053400392824075, "is_lower_bound": false, "measured_at": "2026-10-08T11:46:26.206000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-08T11:46:26.206000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-08T11:46:26.206000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-107574" } } }
published 2026-10-12 01:37Z
last change 2026-10-21 04: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.