Skip to content

← Public intelligence

Packagist package

cpsit/typo3-mailqueue

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.2PackagistPublished

    The mailqueue TYPO3 extension has Insecure Deserialization in TransportFailure class

    CVE-2026-1323 · GHSA-2pm6-9fhx-vvg3

    Affected
    • Packagist cpsit/typo3-mailqueue < 0.4.5; >= 0.5.0, < 0.5.2
    Fixed in
    0.5.20.4.5· Vendor fix available
    Issue
    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['TYPO3CONFVARS']['MAIL']['transportspoolfilepath'].

    Recommended action: Upgrade to 0.5.2 or 0.4.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 5.2PackagistPublished

    mailqueue TYPO3 extension affected by Insecure Deserialization in QueueableFileTransport

    CVE-2026-0895 · GHSA-ggff-9mj3-7246

    Affected
    • Packagist cpsit/typo3-mailqueue < 0.4.3; >= 0.5.0, < 0.5.1
    Fixed in
    0.4.30.5.1· Vendor fix available
    Issue
    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 TYPO3-EXT-SA-2026-001 https://github.com/CPS-IT/mailqueue/commit/fd09aa4e1a751551bae4b228bee814e22f2048db https://github.com/CPS-IT/mailqueue/commit/12a0a35027bb5609917790a94e43bbf117abf733

    Recommended action: Upgrade to 0.5.1 or 0.4.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →