TYPO3 CMS up to 14.3.2 Storage Backend or deserialization

Summaryinfo

A vulnerability was found in TYPO3 CMS up to 10.4.56/11.5.50/12.4.45/13.4.30/14.3.2. It has been classified as problematic. This vulnerability affects the function or of the component Storage Backend. This manipulation causes deserialization. This vulnerability appears as CVE-2026-49740. The attack requires local access. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in TYPO3 CMS up to 10.4.56/11.5.50/12.4.45/13.4.30/14.3.2. It has been declared as problematic. Affected by this vulnerability is the function or of the component Storage Backend. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.51, 12.0.0-12.4.46, 13.0.0-13.4.31 and 14.0.0-14.3.3.

The advisory is shared at typo3.org. This vulnerability is known as CVE-2026-49740 since 06/01/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.

Upgrading to version 10.4.57, 11.5.51, 12.4.46, 13.4.31 or 14.3.3 eliminates this vulnerability. Applying the patch 48bcf24f31f52cc0b43d3bea4984634bd2cf85c7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1835). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• TYPO3 Core

Productinfo

Type

• Content Management System

Vendor

• TYPO3

Name

• CMS

Version

• 10.4.0
• 10.4.1
• 10.4.2
• 10.4.3
• 10.4.4
• 10.4.5
• 10.4.6
• 10.4.7
• 10.4.8
• 10.4.9
• 10.4.10
• 10.4.11
• 10.4.12
• 10.4.13
• 10.4.14
• 10.4.15
• 10.4.16
• 10.4.17
• 10.4.18
• 10.4.19
• 10.4.20
• 10.4.21
• 10.4.22
• 10.4.23
• 10.4.24
• 10.4.25
• 10.4.26
• 10.4.27
• 10.4.28
• 10.4.29
• 10.4.30
• 10.4.31
• 10.4.32
• 10.4.33
• 10.4.34
• 10.4.35
• 10.4.36
• 10.4.37
• 10.4.38
• 10.4.39
• 10.4.40
• 10.4.41
• 10.4.42
• 10.4.43
• 10.4.44
• 10.4.45
• 10.4.46
• 10.4.47
• 10.4.48
• 10.4.49
• 10.4.50
• 10.4.51
• 10.4.52
• 10.4.53
• 10.4.54
• 10.4.55
• 10.4.56
• 11.5.0
• 11.5.1
• 11.5.2
• 11.5.3
• 11.5.4
• 11.5.5
• 11.5.6
• 11.5.7
• 11.5.8
• 11.5.9
• 11.5.10
• 11.5.11
• 11.5.12
• 11.5.13
• 11.5.14
• 11.5.15
• 11.5.16
• 11.5.17
• 11.5.18
• 11.5.19
• 11.5.20
• 11.5.21
• 11.5.22
• 11.5.23
• 11.5.24
• 11.5.25
• 11.5.26
• 11.5.27
• 11.5.28
• 11.5.29
• 11.5.30
• 11.5.31
• 11.5.32
• 11.5.33
• 11.5.34
• 11.5.35
• 11.5.36
• 11.5.37
• 11.5.38
• 11.5.39
• 11.5.40
• 11.5.41
• 11.5.42
• 11.5.43
• 11.5.44
• 11.5.45
• 11.5.46
• 11.5.47
• 11.5.48
• 11.5.49
• 11.5.50
• 12.4.0
• 12.4.1
• 12.4.2
• 12.4.3
• 12.4.4
• 12.4.5
• 12.4.6
• 12.4.7
• 12.4.8
• 12.4.9
• 12.4.10
• 12.4.11
• 12.4.12
• 12.4.13
• 12.4.14
• 12.4.15
• 12.4.16
• 12.4.17
• 12.4.18
• 12.4.19
• 12.4.20
• 12.4.21
• 12.4.22
• 12.4.23
• 12.4.24
• 12.4.25
• 12.4.26
• 12.4.27
• 12.4.28
• 12.4.29
• 12.4.30
• 12.4.31
• 12.4.32
• 12.4.33
• 12.4.34
• 12.4.35
• 12.4.36
• 12.4.37
• 12.4.38
• 12.4.39
• 12.4.40
• 12.4.41
• 12.4.42
• 12.4.43
• 12.4.44
• 12.4.45
• 13.4.0
• 13.4.1
• 13.4.2
• 13.4.3
• 13.4.4
• 13.4.5
• 13.4.6
• 13.4.7
• 13.4.8
• 13.4.9
• 13.4.10
• 13.4.11
• 13.4.12
• 13.4.13
• 13.4.14
• 13.4.15
• 13.4.16
• 13.4.17
• 13.4.18
• 13.4.19
• 13.4.20
• 13.4.21
• 13.4.22
• 13.4.23
• 13.4.24
• 13.4.25
• 13.4.26
• 13.4.27
• 13.4.28
• 13.4.29
• 13.4.30
• 14.3.0
• 14.3.1
• 14.3.2

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion