Answer in brief
CVE-2026-61815 records a High severity (CVSS 7.2) vulnerability in zbateson/mail-mime-parser has CRLF header injection via attachment filename. 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). 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.2. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| zbateson/mail-mime-parsercomposer | <3.0.6 | 3.0.6 |
| zbateson/mail-mime-parsercomposer | >=4.0.0,<4.0.2 | 4.0.2 |
| zbateson/mail-mime-parsergeneric | <3.0.6 || >=4.0.0 <4.0.2 | 3.0.6, 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. 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).
Quoted source text, attributed separately from HOL analysis.