Local code execution via unrestricted spool deserialization
Published Jan 13, 2026 · Updated Jan 13, 2026
Insecure deserialization in the TYPO3 CMS Mailer allows local users to execute arbitrary PHP through a crafted mail spool file. FileSpool passes attacker-controlled serialized data to PHP unserialize with a misspelled allowed_classes option, leaving the intended class restriction ineffective. Exploitation requires file-spool mail transport, write access to its spool directory, and a scheduler or cron invocation of mailer:spool:send.
Summary
What happened
Insecure deserialization in the TYPO3 CMS Mailer allows local users to execute arbitrary PHP through a crafted mail spool file. FileSpool passes attacker-controlled serialized data to PHP unserialize with a misspelled allowed_classes option, leaving the intended class restriction ineffective. Exploitation requires file-spool mail transport, write access to its spool directory, and a scheduler or cron invocation of mailer:spool:send.
The record
- CVE
- CVE-2026-0859
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- in2code GmbH
- Product
- TYPO3 CMS
- Classifications
- CWE-502, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 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=10.0.0 <10.4.55
- Affected versionversion=11.0.0 <11.5.49
- Affected versionversion=12.0.0 <12.4.41
- Affected versionversion=13.0.0 <13.4.23
- Affected versionversion=14.0.0 <14.0.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.
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