GHSA-2pm6-9fhx-vvg3 is a high-severity (CVSS 8.8) Deserialization of Untrusted Data vulnerability in cpsit/typo3-mailqueue. A fix is available for cpsit/typo3-mailqueue — see the affected versions and patch details below.
The mailqueue TYPO3 extension has Insecure Deserialization in `TransportFailure` class
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2pm6-9fhx-vvg3.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-2pm6-9fhx-vvg3 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
cpsit/typo3-mailqueue🐘cpsit/typo3-mailqueueReal-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
Description
The extension fails to properly define allowed classes used when deserializing transport failure metadata. An attacker may exploit this to execute untrusted serialized code. Note that an active exploit requires write access to the directory configured at $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_filepath'].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cpsit/typo3-mailqueue | all versions | 0.4.5composer require cpsit/typo3-mailqueue:^0.4.5 |
| 🐘Packagist | cpsit/typo3-mailqueue | ≥ 0.5.0&&< 0.5.2 | 0.5.2composer require cpsit/typo3-mailqueue:^0.5.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cpsit/typo3-mailqueue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cpsit/typo3-mailqueue to 0.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pm6-9fhx-vvg3 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-2pm6-9fhx-vvg3 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2pm6-9fhx-vvg3. 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-2pm6-9fhx-vvg3 in your dependencies?
O3 Security finds GHSA-2pm6-9fhx-vvg3 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.