Local code execution via unrestricted spool deserialization
Published Jan 20, 2026 · Updated Jan 20, 2026
Insecure deserialization in TYPO3 Mailqueue before 0.4.3 and 0.5.0 allows local users to execute code through crafted spool files. QueueableFileTransport passes the unsupported allowedClasses key to PHP unserialize(), so PHP ignores the intended class allowlist when restoring serialized messages from disk. Exploitation requires write access to the configured mail spool directory; successful object injection runs code in the TYPO3 process context.
Summary
What happened
Insecure deserialization in TYPO3 Mailqueue before 0.4.3 and 0.5.0 allows local users to execute code through crafted spool files. QueueableFileTransport passes the unsupported allowedClasses key to PHP unserialize(), so PHP ignores the intended class allowlist when restoring serialized messages from disk. Exploitation requires write access to the configured mail spool directory; successful object injection runs code in the TYPO3 process context.
The record
- CVE
- CVE-2026-0895
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- in2code GmbH
- Product
- Mailqueue
- Classifications
- CWE-502
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 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.3
- Affected versionversion=0.5.0 <0.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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