GHSA-ggff-9mj3-7246 — cpsit/typo3-mailqueue
Fix: CPS-IT/mailqueue@12a0a35GHSA-ggff-9mj3-7246 is a 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.
mailqueue TYPO3 extension affected by Insecure Deserialization in QueueableFileTransport
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-ggff-9mj3-7246.
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.
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 extends TYPO3’s FileSpool component, which was vulnerable to Insecure Deserialization prior to TYPO3-CORE-SA-2026-004. Since the related fix is overwritten by the extension, using the extension with a patched TYPO3 core version still allows for Insecure Deserialization, because the affected vulnerable code was extracted from TYPO3 core to the extension.
More information about this vulnerability can be found in the related TYPO3 Core Security Advisory TYPO3-CORE-SA-2026-004.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cpsit/typo3-mailqueue | all versions | 0.4.3composer require cpsit/typo3-mailqueue:^0.4.3 |
| 🐘Packagist | cpsit/typo3-mailqueue | ≥ 0.5.0&&< 0.5.1 | 0.5.1composer require cpsit/typo3-mailqueue:^0.5.1 |
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.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggff-9mj3-7246 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-ggff-9mj3-7246 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-ggff-9mj3-7246. 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-ggff-9mj3-7246 in your dependencies?
O3 Security finds GHSA-ggff-9mj3-7246 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.