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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4qpj-gxxg-jqg4 can be triaged on real exposure rather than presence alone.

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

Not in CISA KEV

GHSA-4qpj-gxxg-jqg4 — swiftmailer/swiftmailer

Fix: swiftmailer/swiftmailer@b4b78af

GHSA-4qpj-gxxg-jqg4 is a security vulnerability in swiftmailer/swiftmailer. A fix is available for swiftmailer/swiftmailer — see the affected versions and patch details below.

Swiftmailer Sendmail transport arbitrary shell execution

Published

May 29, 2024

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 4, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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`composer require swiftmailer/swiftmailer:^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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4qpj-gxxg-jqg4 can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-4qpj-gxxg-jqg4 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works