CVE-2026-1323: The extension fails to properly define allowed classes used when deserializing transport failure metadata
CVE-2026-1323 is a high-severity flaw (CVSS 8.8) affecting mailqueue. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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'].
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 87%) |
| CISA exploited list | No |
| Weakness | CWE-502 |
| Published | 2026-03-17 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-1323?
mailqueue: upgrade to 0.4.5, 0.5.2. Exact commands for each OS are on this page.
Is CVE-2026-1323 being exploited?
CVE-2026-1323 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-1323 affect?
CVE-2026-1323 affects mailqueue. Severity is high (CVSS 8.8). 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
How urgent is CVE-2026-1323?
Priority 34/100. High severity