CVE-2026-126613

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

GHSA-68qj-r5q8-pvm5 ↗EUVD-2026-123326 ↗

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.2, <= 6.3.7
fixed in 6.3.6
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-4152Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 46msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h34m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

hMailServer's JSON reader can allow remote attackers to exhaust memory and worker threads, disrupting mail delivery, webmail, the REST API, and related services. Exposure depends on a reachable JSON-processing path, such as configured TLS-RPT report mailboxes, enabled public REST password-message links, or authenticated webmail and API access; the supplied evidence conflicts on the affected version range.

mitigation

Upgrade hMailServer to version 6.3.6. Until upgraded, disable the REST API where it is not required and avoid exposing or configuring the affected report-mailbox and public-link entry points where operationally feasible.

fixed in 6.3.6

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
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

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:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4152",
  "cve_id": "CVE-2026-126613",
  "display_id": "CVE-2026-126613",
  "ghsa_id": "GHSA-68qj-r5q8-pvm5",
  "euvd_id": "EUVD-2026-123326",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Resource exhaustion in hMailServer JSON reader",
  "summary": "hMailServer's JSON reader can allow remote attackers to exhaust memory and worker threads, disrupting mail delivery, webmail, the REST API, and related services. Exposure depends on a reachable JSON-processing path, such as configured TLS-RPT report mailboxes, enabled public REST password-message links, or authenticated webmail and API access; the supplied evidence conflicts on the affected version range.",
  "mitigation": "Upgrade hMailServer to version 6.3.6. Until upgraded, disable the REST API where it is not required and avoid exposing or configuring the affected report-mailbox and public-link entry points where operationally feasible.",
  "vendor": "Progressive Robot Ltd",
  "product": "hMailServer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.3.2, <= 6.3.7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.3.6"
      ],
      "package_name": "hMailServer",
      "purl": null
    }
  ],
  "cwes": [
    770
  ],
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 17.572507333333334,
  "t0_at": "2026-11-11T08:31:12.127000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T08:31:12.127000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-11T08:31:12.127000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-126613"
    }
  }
}

published 2026-11-11 08:47Z
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.