GitHub Advisoryadvisory · Packagist

GHSA-c78m-c52x-jgwp TYPO3 CMS has Insecure Deserialization via Core API

MEDIUM Published 2026-06-12 Modified 2026-06-12 Official page ↗
Aliases
CVE-2026-49740
Ecosystem
Packagist
Packages
typo3/cms-core
Severity
Moderate
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:H/SI:H/SA:H
Weaknesses
CWE-502
Reviewed
2026-06-12

Affected packages

• Packagist typo3/cms-core: < 10.4.57 → fixed in 10.4.57 • Packagist typo3/cms-core: >= 11.0.0, < 11.5.51 → fixed in 11.5.51 • Packagist typo3/cms-core: >= 12.0.0, < 12.4.46 → fixed in 12.4.46 • Packagist typo3/cms-core: >= 13.0.0, < 13.4.31 → fixed in 13.4.31 • Packagist typo3/cms-core: >= 14.0.0, < 14.3.3 → fixed in 14.3.3

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 • TYPO3-CORE-SA-2026-018

Related

Alias · CVE (1)

  • CVE-2026-49740 TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation… vulnerability

Weakness · CWE (1)

  • CWE-502 Deserialization of Untrusted Data weakness

References