typo3/cms-core
Affected
- introduced
0, fixed10.4.57(ecosystem)
Fixed versions
10.4.57
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-49740
TYPO3 CMS has Insecure Deserialization via Core API
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
Medium Basis: The source's own band: MODERATE
0, fixed 10.4.57 (ecosystem)10.4.57
The export has no generic command for this ecosystem.
11.0.0, fixed 11.5.51 (ecosystem)11.5.51
The export has no generic command for this ecosystem.
12.0.0, fixed 12.4.46 (ecosystem)12.4.46
The export has no generic command for this ecosystem.
13.0.0, fixed 13.4.31 (ecosystem)13.4.31
The export has no generic command for this ecosystem.
14.0.0, fixed 14.3.3 (ecosystem)14.3.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0