MediumGHSA-c78m-c52x-jgwpCVE-2026-49740

TYPO3 CMS has Insecure Deserialization via Core API

Published 12 Jun 2026 · Updated 10 Sept 2026

Affected packages

typo3/cms-coreComposer
Affected
<10.4.57
Fixed in
10.4.57
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.57
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.51
Fixed in
11.5.51
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.51
typo3/cms-coreComposer
Affected
>=12.0.0 <12.4.46
Fixed in
12.4.46
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.4.46
typo3/cms-coreComposer
Affected
>=13.0.0 <13.4.31
Fixed in
13.4.31
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^13.4.31
typo3/cms-coreComposer
Affected
>=14.0.0 <14.3.3
Fixed in
14.3.3
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^14.3.3

Details

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

Is GHSA-c78m-c52x-jgwp in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.