OCTOBER 9, 2026
Live Feed
Back to database
Case File

CVE-2026-61815

HIGH · CVSS 7.2 EPSS 0.18% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-24 · Last synced 2026-10-09

CyberRota Analysis

AI-Generated

The zbateson/mail-mime-parser library is vulnerable to CRLF header injection, allowing attackers to manipulate attachment filenames in MIME messages, potentially leading to unauthorized header injection and message exfiltration. This issue affects any application using the library versions prior to 3.0.6 and 4.0.2, particularly those that handle user-controlled filenames from inbound emails. Developers and organizations utilizing this library should prioritize upgrading to a patched version or implement immediate mitigations by sanitizing filenames to prevent exploitation.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-61815
Severity
HIGH
CVSS
7.2
EPSS
0.18%

Original NVD Description

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).