CVE Catalog

CVE-2026-61815

HighCVSS 7.2
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.18%

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

Summary

The zbateson/mail-mime-parser library prior to versions 3.0.6 and 4.0.2 is vulnerable to CRLF header injection (CWE-93) when building MIME messages with attacker-influenced attachment filenames. Filenames containing CR/LF can be serialized as additional header lines, such as a forged Bcc, enabling message exfiltration. Versions 1.x and 2.x are also affected but are end-of-life and will not receive patches.

Risk Assessment

An attacker could exploit this to intercept copies of outgoing emails, leading to confidentiality breaches. Applications processing attachments from untrusted sources are particularly at risk.

Recommendation

Upgrade to version 3.0.6 or 4.0.2. If immediate upgrade is not possible, strip CR and LF from filenames before passing them to attachment APIs and from the result of getFilename() before reuse.

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. Prior to version 3.0.6 and 4.0.2, CRLF (carriage-return / line-feed) header injection (CWE-93) affecting any application that uses this library to build or forward MIME messages with an attacker-influenced attachment filename. Attachment filenames are interpolated into the `Content-Type` and `Content-Disposition` header values without stripping CR/LF, so a filename containing `\r\n` serializes as one or more additional, attacker-controlled header lines (for example a forged `Bcc:` that silently exfiltrates a copy of the outgoing message). The untrusted filename can come directly from parsed inbound mail, so no local construction is required — an application that re-attaches or re-sends a parsed filename is exposed. Versions 3.0.6 and 4.0.2 patch the issue. Versions 1.x and 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. If upgrading is not immediately possible, strip CR and LF from any filename before passing it to attachment APIs, and from the result of getFilename() before reusing it in a constructed message — e.g. preg_replace('/[\r\n]+/', ' ', $filename).

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