GHSA-45xg-4w5x-j429
HIGHTYPO3 Arbitrary Shell Execution in Swiftmailer library
Blast Radius
typo3/cms🐘typo3/cms🐘typo3/cms🐘typo3/cmsReal-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
The swiftmailer library in use allows to execute arbitrary shell commands if the "From" header comes from a non-trusted source and no "Return-Path" is configured. Affected are only TYPO3 installation the configuration option
$GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport']
is set to "sendmail". Installations with the default configuration are not affected.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms | ≥ 6.2.0&&< 6.2.6 | 6.2.6 |
| 🐘Packagist | typo3/cms | ≥ 6.1.0&&< 6.1.12 | 6.1.12 |
| 🐘Packagist | typo3/cms | ≥ 4.7.0&&< 4.7.20 | 4.7.20 |
| 🐘Packagist | typo3/cms | ≥ 4.5.0&&< 4.5.37 | 4.5.37 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms. 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 typo3/cms to 6.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-45xg-4w5x-j429 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-45xg-4w5x-j429 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-45xg-4w5x-j429. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-45xg-4w5x-j429 in your dependencies?
O3 detects GHSA-45xg-4w5x-j429 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.