Is neos/swiftmailer 5.2 vulnerable?

Composer · 1 release from 5.2.2 to 5.2.2 · latest neos/swiftmailer is 7.4.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. neos/swiftmailer 5.2.2, the last 5.2 release, is affected by 1 known security advisory (1 critical). Upgrade to 5.4.5 or later to fix all of them.

Upgrade with:composer require neos/swiftmailer:^5.4.5

Is your project on an affected neos/swiftmailer?

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 neos/swiftmailer 5.2.2

  • CriticalGHSA-rq6q-hjvh-5mwh17 May 2024

    Flow Swift Mailer package Remote code execution

    Affected
    <5.4.5
    Fixed in
    5.4.5

Which of your client projects are still on neos/swiftmailer 5.2?

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

Other neos/swiftmailer 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.