Code execution via misspelled deserialization allowlist
Published Mar 17, 2026 · Updated Mar 17, 2026
Insecure deserialization in TYPO3 Mailqueue before 0.4.5 and 0.5.0 through 0.5.1 allows local users to execute untrusted serialized code. TransportFailure::fromFile reads spool metadata into PHP unserialize(), but misspells allowed_classes as allowedClasses, so PHP applies no class allowlist. Exploitation requires write access to the configured mail transport spool directory and can execute gadget code in the TYPO3 process context.
Summary
What happened
Insecure deserialization in TYPO3 Mailqueue before 0.4.5 and 0.5.0 through 0.5.1 allows local users to execute untrusted serialized code. TransportFailure::fromFile reads spool metadata into PHP unserialize(), but misspells allowed_classes as allowedClasses, so PHP applies no class allowlist. Exploitation requires write access to the configured mail transport spool directory and can execute gadget code in the TYPO3 process context.
The record
- CVE
- CVE-2026-1323
- Published
- Mar 17, 2026
- Updated
- Mar 17, 2026
- Vendor
- in2code GmbH
- Product
- Mailqueue
- Classifications
- CWE-502, CAPEC-586
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 17, 2026CVE publishedPublication date reported by the CVE source.
- Mar 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.4.5
- Affected versionversion=0.5.0 <0.5.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo