ETK-2026-1965Zero's internal tracking ID, independent of the CVE number.

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

GHSA-f2hq-32vh-53cc ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:postal-mime >= 3.0.0, < 4.0.8
fixed in 4.0.8
CWE-400 Uncontrolled Resource Consumption
ETK-2026-1965Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/postal-mime
2d 16h 54msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dwaiting for further signals+0.1d
+1d
+2d
+3d

description

postal-mime 3.0.0 through 4.0.7 can spend excessive CPU time decoding email headers containing many joinable RFC 2047 encoded words. An attacker able to submit email that the application parses can block the event loop and cause denial of service.

mitigation

Upgrade postal-mime to version 4.0.8. Until upgraded, lower maxHeadersSize and parse untrusted mail in a worker that can be terminated.

fixed in 4.0.8

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
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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: an exploit technique exists, 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.

  1. 2026-10-18 10:08Z

this entry in the feed

GET /api/v1/feed/ETK-2026-1965

{
  "etk_id": "ETK-2026-1965",
  "cve_id": null,
  "display_id": "ETK-2026-1965",
  "ghsa_id": "GHSA-f2hq-32vh-53cc",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Quadratic header decoding denial of service in postal-mime",
  "summary": "postal-mime 3.0.0 through 4.0.7 can spend excessive CPU time decoding email headers containing many joinable RFC 2047 encoded words. An attacker able to submit email that the application parses can block the event loop and cause denial of service.",
  "mitigation": "Upgrade postal-mime to version 4.0.8. Until upgraded, lower maxHeadersSize and parse untrusted mail in a worker that can be terminated.",
  "vendor": "npm",
  "product": "npm:postal-mime",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0, < 4.0.8"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "4.0.8"
      ],
      "package_name": "postal-mime",
      "purl": "pkg:npm/postal-mime"
    }
  ],
  "cwes": [
    400
  ],
  "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": 11.507207066666666,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-18T10:08:36+00:00",
      "days": -2.779705531215278,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T04:51:22.579725+00:00",
      "url": "https://github.com/postalsys/postal-mime/security/advisories/GHSA-f2hq-32vh-53cc"
    }
  }
}

published 2026-10-18 11:45Z
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.