How severe is GHSA-4qpj-gxxg-jqg4?

No CVSS score has been assigned to GHSA-4qpj-gxxg-jqg4 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4qpj-gxxg-jqg4?

GHSA-4qpj-gxxg-jqg4 affects the following packages: swiftmailer/swiftmailer (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4qpj-gxxg-jqg4?

Update swiftmailer/swiftmailer to 5.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qpj-gxxg-jqg4 is resolved across your whole dependency graph.

How do I detect GHSA-4qpj-gxxg-jqg4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swiftmailer/swiftmailer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-4qpj-gxxg-jqg4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-4qpj-gxxg-jqg4?

O3 pinpoints whether GHSA-4qpj-gxxg-jqg4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4qpj-gxxg-jqg4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-4qpj-gxxg-jqg4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-4qpj-gxxg-jqg4 published, and has it been updated?

GHSA-4qpj-gxxg-jqg4 was published on May 29, 2024 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-4qpj-gxxg-jqg4

GHSA-4qpj-gxxg-jqg4 is a security vulnerability in swiftmailer/swiftmailer. O3 Security confirms whether GHSA-4qpj-gxxg-jqg4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Swiftmailer Sendmail transport arbitrary shell execution

Published

May 29, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐘swiftmailer/swiftmailer

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Prior to 5.2.1, the sendmail transport (Swift_Transport_SendmailTransport) was vulnerable to an arbitrary shell execution if the "From" header came from a non-trusted source and no "Return-Path" is configured. This has been fixed in 5.2.1. If you are using sendmail as a transport, you are encouraged to upgrade as soon as possible.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`swiftmailer/swiftmailer`	≥ 4.0.0&&< 5.2.1	5.2.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for swiftmailer/swiftmailer. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update swiftmailer/swiftmailer to 5.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4qpj-gxxg-jqg4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4qpj-gxxg-jqg4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-4qpj-gxxg-jqg4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Prior to 5.2.1, the sendmail transport (`Swift_Transport_SendmailTransport`) was vulnerable to an arbitrary shell execution if the "From" header came from a non-trusted source and no "Return-Path" is configured. This has been fixed in 5.2.1. If you are using sendmail as a transport, you are encouraged to upgrade as soon as possible.

O3 Security · Impact-Aware SCA

Is GHSA-4qpj-gxxg-jqg4 in your dependencies?

O3 detects GHSA-4qpj-gxxg-jqg4 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works