Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.2amended

zbateson/mail-mime-parser has CRLF header injection via attachment filename

CVE-2026-61815GHSA-36h5-qg4p-q2qf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (zbateson/mail-mime-parser 4.0.2, 3.0.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
EPSS
  • CVE-2026-61815: 0.18% estimated exploitation activity in the next 30 days; percentile 7.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A CRLF (carriage-return / line-feed) header injection 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. Details On the outbound side, MultipartHelper::createAndAddPartForAttachment() sanitizes the filename only with iconv('UTF-8','US-ASCII//translit//ignore', $filename). CR and LF are valid US-ASCII, so they survive that filter, and the value is then written into the header verbatim via MimePart::setRawHeader(). A…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-36h5-qg4p-q2qf

  2. Revision 1 · created ·

    Published from osv record GHSA-36h5-qg4p-q2qf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61815

Advisory: zbateson/mail-mime-parser has CRLF header injection via attachment filename
IDs: CVE-2026-61815, GHSA-36h5-qg4p-q2qf
Record: https://patchnext.com/advisories/cve-2026-61815 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: zbateson/mail-mime-parser 4.0.2, 3.0.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist zbateson/mail-mime-parser: affected < 3.0.6; >= 4.0.0, < 4.0.2; fixed in 3.0.6, 4.0.2

## Suggested inspection (read-only)
- Packagist zbateson/mail-mime-parser: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on zbateson/mail-mime-parser.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-36h5-qg4p-q2qf (OSV record GHSA-36h5-qg4p-q2qf lists affected ranges: Packagist zbateson/mail-mime-parser >=0 =4.0.0 <4.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-36h5-qg4p-q2qf (GitHub-reviewed advisory GHSA-36h5-qg4p-q2qf lists affected ranges: Packagist zbateson/mail-mime-parser >=0 =4.0.0 <4.0.2)

Commands are suggestions: review each one before running it.

Loading voting…