Skip to content
Fencer Intel
high 7.8

CVE-2026-0859 json

TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool

published 9mo ago modified 4mo ago also GHSA-7vp9-x248-9vr9 , EUVD-2026-2014

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

TYPO3's mail‑file spool deserialization flaw lets local users with write access to the spool directory craft a malicious file that is deserialized during the mailer:spool:send command, enabling arbitrary PHP code execution on the web server. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.

Patch / fix

  • packagist typo3/cms-core 10.4.55, 11.5.49, 12.4.41, 13.4.23, 14.0.2
  • TYPO3 TYPO3 CMS 10.4.55, 11.5.49, 12.4.41, 13.4.23, 14.0.2

Is CVE-2026-0859 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
9mo ago

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 5.2 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H
CNA 4.0 5.2 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-core
>=14.0.0, <14.0.2
>=13.0.0, <13.4.23
>=12.0.0, <12.4.41
>=11.0.0, <11.5.49
>=10.0.0, <10.4.55
14.0.2
13.4.23
12.4.41
11.5.49
10.4.55

Affected products

  • TYPO3 TYPO3 CMS

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.