All reports
Medium

TYPO3 CMS has Insecure Deserialization via Core API

Affected versions

Version ranges need review.

Affected versions
>= 14.0.0, < 14.3.3
Fixed version
14.3.3
Affected versions
>= 11.0.0, < 11.5.51
Fixed version
11.5.51
Affected versions
>= 12.0.0, < 12.4.46
Fixed version
12.4.46
Affected versions
<10.4.57|>=11.0.0,<11.5.51|>=12.0.0,<12.4.46|>=13.0.0,<13.4.31|>=14.0.0,<14.3.3
Fixed version
Not reported
Affected versions
>= 13.0.0, < 13.4.31
Fixed version
13.4.31
Affected versions
< 10.4.57
Fixed version
10.4.57

Exploitation

CVE-2026-49740

Probability of exploitation in the next 30 days: 0.22%

FIRST EPSS · 2026-11-21

Description

Problem

TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted serialized payload to trigger PHP Object Injection, potentially exploiting a gadget chain to achieve Remote Code Execution or other high-impact effects.

Exploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system.

Solution

Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits

TYPO3 CMS thanks “z3rco”, Chowdhury Faizal Ahammed, Rick Larabee, Vitaly Simonovich, Nozomu Sasaki, Mert Akdag, “tikket”, Shafi Almutairi for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.

Resources

Links