How severe is GHSA-rq6q-hjvh-5mwh?

No CVSS score has been assigned to GHSA-rq6q-hjvh-5mwh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rq6q-hjvh-5mwh?

GHSA-rq6q-hjvh-5mwh affects the following packages: neos/swiftmailer (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rq6q-hjvh-5mwh?

Update neos/swiftmailer to 5.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rq6q-hjvh-5mwh is resolved across your whole dependency graph.

How do I detect GHSA-rq6q-hjvh-5mwh in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/swiftmailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rq6q-hjvh-5mwh 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-rq6q-hjvh-5mwh?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rq6q-hjvh-5mwh can be triaged on real exposure rather than presence alone.

Is GHSA-rq6q-hjvh-5mwh actively exploited in the wild?

No public exploit code has been indexed for GHSA-rq6q-hjvh-5mwh 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-rq6q-hjvh-5mwh published, and has it been updated?

GHSA-rq6q-hjvh-5mwh was published on May 17, 2024 and was last updated on December 2, 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-rq6q-hjvh-5mwh — neos/swiftmailer

GHSA-rq6q-hjvh-5mwh is a remote code execution vulnerability in neos/swiftmailer. A fix is available for neos/swiftmailer — see the affected versions and patch details below.

Flow Swift Mailer package Remote code execution

Published

May 17, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐘neos/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

A remote code execution vulnerability has been found in the Swift Mailer library (swiftmailer/swiftmailer) recently. See this advisory for details. If you are not using the default mail() transport, this particular problem does not affect you. Upgrading is of course still recommended!

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`neos/swiftmailer`	all versions	5.4.5`composer require neos/swiftmailer:^5.4.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/swiftmailer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update neos/swiftmailer to 5.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rq6q-hjvh-5mwh 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-rq6q-hjvh-5mwh can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rq6q-hjvh-5mwh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A remote code execution vulnerability has been found in the Swift Mailer library (swiftmailer/swiftmailer) recently. [See this advisory for details](http://legalhackers.com/advisories/SwiftMailer-Exploit-Remote-Code-Exec-CVE-2016-10074-Vuln.html). If you are not using the default mail() transport, this particular problem does not affect you. Upgrading is of course still recommended!

O3 Security · Impact-Aware SCA

Is GHSA-rq6q-hjvh-5mwh in your dependencies?

O3 Security finds GHSA-rq6q-hjvh-5mwh 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