All reports
Medium

TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool

Affected versions

Affected versions
>= 14.0.0, <= 14.0.1
Fixed version
14.0.2
Affected versions
>= 11.0.0, <= 11.5.48
Fixed version
11.5.49
Affected versions
>= 13.0.0, <= 13.4.22
Fixed version
13.4.23
Affected versions
>= 10.0.0, <= 10.4.54
Fixed version
10.4.55
Affected versions
>= 12.0.0, <= 12.4.40
Fixed version
12.4.41

Exploitation

CVE-2026-0859

Probability of exploitation in the next 30 days: 0.18%

FIRST EPSS · 2026-11-21

Description

Problem

Local platform users who can write to TYPO3’s mail‑file spool directory can craft a file that the system will automatically deserialize without any class restrictions. This flaw allows an attacker to inject and execute arbitrary PHP code in the public scope of the web server.

The vulnerability is triggered when TYPO3 is configured with $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_type'] = 'file'; and a scheduler task or cron job runs the command mailer:spool:send. The spool‑send operation performs the insecure deserialization that is at the core of this issue.

Solution

Update to TYPO3 versions 10.4.55 ELTS, 11.5.49 ELTS, 12.4.41 LTS, 13.4.23 LTS, 14.0.2 that fix the problem described.

Credits

Thanks to Vitaly Simonovich for reporting this issue, and to TYPO3 security team members Elias Häußler and Oliver Hader for fixing it.

References

Links

Credits

  • eliashaeussler
  • ohader