Is zbateson/mail-mime-parser 2.0 vulnerable?

Composer · 2 releases from 2.0.0 to 2.0.1 · latest zbateson/mail-mime-parser is 4.0.9 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. zbateson/mail-mime-parser 2.0.1, the last 2.0 release, is affected by 2 known security advisories (2 high), including CVE-2026-61815, CVE-2026-61816. Upgrade to 3.0.6 or later to fix all of them.

Upgrade with:composer require zbateson/mail-mime-parser:^3.0.6

Is your project on an affected zbateson/mail-mime-parser?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting zbateson/mail-mime-parser 2.0.1

  • HighCVE-2026-61815GHSA-36h5-qg4p-q2qf24 Sept 2026

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

    Affected
    <3.0.6 · >=4.0.0 <4.0.2
    Fixed in
    3.0.6, 4.0.2
  • HighCVE-2026-61816GHSA-f6v3-2qmr-vfjx24 Sept 2026

    zbateson/mail-mime-parser has uncontrolled resource consumption (CPU/memory DoS) parsing untrusted MIME

    Affected
    >=2.0.0 <3.0.6 · >=4.0.0 <4.0.2
    Fixed in
    3.0.6, 4.0.2

Every zbateson/mail-mime-parser 2.0.x release

Affected: 2.0.0 to 2.0.1. Latest zbateson/mail-mime-parser: 4.0.9.

VersionKnown advisories
zbateson/mail-mime-parser 2.0.1CVE-2026-61815, CVE-2026-61816
zbateson/mail-mime-parser 2.0.0CVE-2026-61815, CVE-2026-61816

Which of your client projects are still on zbateson/mail-mime-parser 2.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact zbateson/mail-mime-parser version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other zbateson/mail-mime-parser versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.