CVE-2026-126623

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

GHSA-gxm7-28h3-vf9j ↗EUVD-2026-123328 ↗

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.3.6, <= 6.3.7
CWE-407 Inefficient Algorithmic Complexity
ETK-2026-4153Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 55msince last run
2h 18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

hMailServer 6.3.6 and 6.3.7 can spend excessive CPU time parsing specially chosen JSON objects, allowing remote attackers to occupy mail-delivery or REST API workers and disrupt mail, webmail, or API availability. Unauthenticated exposure depends on configured TLS-RPT report mailboxes or on enabling the REST API with public password-protected-message links.

mitigation

Disable the REST API and public password-protected-message links where they are not required, and remove or isolate TLS-RPT report mailbox handling where operationally feasible. Restrict access to JSON-processing webmail and API routes and apply request-size or rate controls at a proxy; no fixed version is recorded in the advisory.

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.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
2h 18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-11 08:31Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-11 08:31Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-126623

{
  "etk_id": "ETK-2026-4153",
  "cve_id": "CVE-2026-126623",
  "display_id": "CVE-2026-126623",
  "ghsa_id": "GHSA-gxm7-28h3-vf9j",
  "euvd_id": "EUVD-2026-123328",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Algorithmic-complexity denial of service in hMailServer JSON parsing",
  "summary": "hMailServer 6.3.6 and 6.3.7 can spend excessive CPU time parsing specially chosen JSON objects, allowing remote attackers to occupy mail-delivery or REST API workers and disrupt mail, webmail, or API availability. Unauthenticated exposure depends on configured TLS-RPT report mailboxes or on enabling the REST API with public password-protected-message links.",
  "mitigation": "Disable the REST API and public password-protected-message links where they are not required, and remove or isolate TLS-RPT report mailbox handling where operationally feasible. Restrict access to JSON-processing webmail and API routes and apply request-size or rate controls at a proxy; no fixed version is recorded in the advisory.",
  "vendor": "Progressive Robot Ltd",
  "product": "hMailServer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.3.6, <= 6.3.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 138.21308618333333,
  "t0_at": "2026-11-11T08:31:47.129000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T08:31:47.129000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T08:31:47.129000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126623"
    }
  }
}

published 2026-11-11 08:47Z
last change 2026-11-11 12:22Z

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.