CVE Catalog

CVE-2026-61816

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.39%

31th percentile - higher than 31% of all known CVEs

Summary

zbateson/mail-mime-parser versions 2.0.0 through 3.0.5 and 4.0.0 through 4.0.1 contain an uncontrolled resource consumption vulnerability (CWE-400). Three independent parsing paths have super-linear cost, so a crafted message under 2 MB can consume seconds of CPU or hundreds of megabytes to multiple gigabytes of memory, causing denial of service. The cost is incurred on the first getAllParts() or content read.

Risk Assessment

An attacker can send a specially crafted email that exhausts memory or CPU on the server, causing service failure or process termination by the OOM killer. A caller-side byte-size cap does not bound the work done and therefore does not prevent the attack.

Recommendation

Upgrade the library to version 4.0.2 or 3.0.6 (or later). Until upgrading, restrict parsing of untrusted input and run parsing under a constrained memory_limit and execution time limit; users on 2.x should migrate to a supported branch.

Other vulnerabilities in zbateson/mail-mime-parser

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS