# GHSA-rq6q-hjvh-5mwh: Flow Swift Mailer package Remote code execution

> Remote code execution in Swift Mailer when using non-default transports, allowing attackers to execute arbitrary code on the server.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2024

## What is GHSA-rq6q-hjvh-5mwh?

GHSA-rq6q-hjvh-5mwh is a code injection vulnerability in neos/swiftmailer, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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!

## Which versions are affected by GHSA-rq6q-hjvh-5mwh?

2 open source packages ship an affected version, including neos/swiftmailer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `neos/swiftmailer` | Packagist | All versions | 5.4.5 |
| `neos/swiftmailer` | Packagist | All versions | 5.4.5 |

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

Upgrade neos/swiftmailer to 5.4.5 or later.

## Is GHSA-rq6q-hjvh-5mwh being exploited?

There is no known exploitation of GHSA-rq6q-hjvh-5mwh in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rq6q-hjvh-5mwh and fix it if it is affected.

What it is: GHSA-rq6q-hjvh-5mwh is a code injection vulnerability in neos/swiftmailer, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-rq6q-hjvh-5mwh in the wild and no public exploit code.

Affected packages and fixed versions:
- neos/swiftmailer (Packagist): affected all versions; fixed in 5.4.5
- neos/swiftmailer (Packagist): affected all versions; fixed in 5.4.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-rq6q-hjvh-5mwh/ (Markdown: https://insights.sbomify.com/GHSA-rq6q-hjvh-5mwh/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rq6q-hjvh-5mwh

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rq6q-hjvh-5mwh/
Summaries are generated and may contain mistakes; the official description above is the record.