Answer in brief
CVE-2026-61816 records a High severity (CVSS 7.5) vulnerability in zbateson/mail-mime-parser has uncontrolled resource consumption (CPU/memory DoS) parsing untrusted MIME. The current sources do not mark it as known exploited. The current feed maps zbateson/mail-mime-parser (composer), zbateson/mail-mime-parser (composer), zbateson/mail-mime-parser (generic), zbateson/mail-mime-parser (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps zbateson/mail-mime-parser (composer), zbateson/mail-mime-parser (composer), zbateson/mail-mime-parser (generic), zbateson/mail-mime-parser (packagist) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| zbateson/mail-mime-parsercomposer | >=2.0.0,<3.0.6 | 3.0.6 |
| zbateson/mail-mime-parsercomposer | >=4.0.0,<4.0.2 | 4.0.2 |
| zbateson/mail-mime-parsergeneric | >=2.0.0 <3.0.6 || >=4.0.0 <4.0.2 | 3.0.6, 4.0.2 |
| zbateson/mail-mime-parserpackagist | >=2.0.0 <3.0.6 | 3.0.6 |
| zbateson/mail-mime-parserpackagist | >=4.0.0 <4.0.2 | 4.0.2 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
zbateson/mail-mime-parser is a mail mime parser alternative to PHP's imap* functions and Pear libraries for reading messages in Internet Message Format RFC 822. Starting in version 2.0.0 and prior to version 3.0.6 and 4.0.2, an uncontrolled resource consumption / algorithmic complexity vulnerability (CWE-400) affects 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. This is fxed 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.) 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.
Quoted source text, attributed separately from HOL analysis.