symfony/mime vulnerabilities

Allows manipulating MIME messages

Registry
Composer
Latest
8.1.7
License
MIT
Source
github.com/symfony/mime (opens the source repository in a new tab)

3 known advisories

The latest version, 8.1.7, is not affected by any of them. Projects on older versions may be.

Update to the latest version:composer require symfony/mime:^8.1.7

Security advisories for symfony/mime

  • MediumGHSA-vqc8-7275-q27227 May 2026

    Symfony has Email Header Injection via Non-Token Characters in Mime Parameter Names

    Affected
    <5.4.52 · >=6.0.0 <6.4.40 · >=7.0.0 <7.4.12 · >=8.0.0 <8.0.12
    Fixed in
    5.4.52, 6.4.40, 7.4.12, 8.0.12
  • HighGHSA-qpmx-3rfj-7rhv27 May 2026

    Symfony has Email Header / SMTP Command Injection via CRLF in Symfony\Component\Mime\Address

    Affected
    <5.4.52 · >=6.0.0 <6.4.40 · >=7.0.0 <7.4.12 · >=8.0.0 <8.0.12
    Fixed in
    5.4.52, 6.4.40, 7.4.12, 8.0.12
  • HighGHSA-xhh6-956q-4q692 Dec 2019

    Argument injection in a MimeTypeGuesser in Symfony

    Affected
    >=4.3.0 <4.3.8
    Fixed in
    4.3.8

Which of your client projects still run an old symfony/mime?

NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other Composer packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.