TYPO3 CMS has Insecure Deserialization via Core API

中 6.3CVE-2026-49740 · GHSA-c78m-c52x-jgwp · 09/06/2026 公開 · 23/07/2026 更新

要点

CVE-2026-49740 は typo3/cms-core に影響する深刻度「中」 (CVSS 6.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.21%（全脆弱性の 12.0% より高い）。
対処：11.5.51, 12.4.46, 13.4.31, 14.3.3 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
typo3/cms-core Packagist	`≥ 11.0.0, < 11.5.51≥ 12.0.0, < 12.4.46≥ 13.0.0, < 13.4.31≥ 14.0.0, < 14.3.3< 10.4.57`	`11.5.5112.4.4613.4.3114.3.310.4.57`

概要

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

TYPO3-CORE-SA-2026-018

NVD の説明

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. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.