{"id":"CVE-2026-49740","aliases":["GHSA-c78m-c52x-jgwp"],"title":"TYPO3 CMS has Insecure Deserialization via Core API","summary":"TYPO3 CMS has Insecure Deserialization via Core API","severity":"medium","cwe":["CWE-502"],"vendor":"typo3","product":"typo3/cms-core","ecosystem":"composer","affected":["typo3/cms-core < 10.4.57","typo3/cms-core >= 11.0.0, < 11.5.51","typo3/cms-core >= 12.0.0, < 12.4.46","typo3/cms-core >= 13.0.0, < 13.4.31","typo3/cms-core >= 14.0.0, < 14.3.3"],"patched":["typo3/cms-core 10.4.57","typo3/cms-core 11.5.51","typo3/cms-core 12.4.46","typo3/cms-core 13.4.31","typo3/cms-core 14.3.3"],"published":"2026-06-12","updated":"2026-06-12","source":"GHSA","sourceUrl":"https://github.com/advisories/GHSA-c78m-c52x-jgwp","references":[{"url":"https://github.com/TYPO3/typo3/security/advisories/GHSA-c78m-c52x-jgwp"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49740"},{"url":"https://github.com/TYPO3/typo3/commit/48bcf24f31f52cc0b43d3bea4984634bd2cf85c7"},{"url":"https://github.com/TYPO3/typo3/commit/87cd7c5b710c44d3606fed277b040a75dc6a9c02"},{"url":"https://github.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2026-49740.yaml"},{"url":"https://typo3.org/security/advisory/typo3-core-sa-2026-018"},{"url":"https://github.com/advisories/GHSA-c78m-c52x-jgwp"}],"tags":["ghsa","composer"],"epss":0.00215,"epssPercentile":0.12209,"ingestedAt":"2026-07-07T15:41:59.174Z","slug":"CVE-2026-49740","body":"## Overview\n\n### Problem\nTYPO3'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.\n\nExploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system.\n\n### Solution\nUpdate 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.\n\n### Credits\nTYPO3 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.\n\n### Resources\n* [TYPO3-CORE-SA-2026-018](https://typo3.org/security/advisory/typo3-core-sa-2026-018)\n\n## Affected packages\n\n- `typo3/cms-core < 10.4.57`\n- `typo3/cms-core >= 11.0.0, < 11.5.51`\n- `typo3/cms-core >= 12.0.0, < 12.4.46`\n- `typo3/cms-core >= 13.0.0, < 13.4.31`\n- `typo3/cms-core >= 14.0.0, < 14.3.3`\n\n## Remediation\n\nUpgrade to a patched release:\n\n- `typo3/cms-core 10.4.57`\n- `typo3/cms-core 11.5.51`\n- `typo3/cms-core 12.4.46`\n- `typo3/cms-core 13.4.31`\n- `typo3/cms-core 14.3.3`","depth":"sunlit","depthScore":28,"depthScoreParts":{"impact":27.5,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}