CVE-2026-49740: TYPO3 CMS - Insecure Deserialization in Core API

Published Jun 9, 2026
·
Updated

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 sysregistry 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

Other sources

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 sysregistry 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.

MITRE

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 sysregistry 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.

NVD

Affected Software

6 affected componentsFixes available
Typo3 TYPO3 CMS<10.4.57, >=11.0.0<=11.5.51, >=12.0.0<=12.4.46, >=13.0.0<=13.4.31, >=14.0.0<=14.3.3
composer/typo3/cms-core>=14.0.0<14.3.3
14.3.3
composer/typo3/cms-core>=13.0.0<13.4.31
13.4.31
composer/typo3/cms-core>=12.0.0<12.4.46
12.4.46
composer/typo3/cms-core>=11.0.0<11.5.51
11.5.51
composer/typo3/cms-core<10.4.57
10.4.57

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 14.3.3
  2. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 13.4.31
  3. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 12.4.46
  4. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 11.5.51
  5. Upgrade

    Upgrade composer/typo3/cms-core to a version that resolves this vulnerability.

    Fixed in 10.4.57
  6. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 10.4.57 ELTS
  7. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 11.5.51 ELTS
  8. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 12.4.46 ELTS
  9. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 13.4.31 LTS
  10. Upgrade

    Upgrade TYPO3 CMS to a version that resolves this vulnerability.

    Fixed in 14.3.3 LTS
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch TYPO3-CORE-SA-2026-018

Event History

Jun 9, 2026
CVE Published
via MITRE·10:53 AM
Data Sourced
via MITRE·10:53 AM
DescriptionWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeakness
Jun 12, 2026
Advisory Published
via GitHub·07:09 PM
Data Sourced
via GitHub·07:09 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-49740?

CVE-2026-49740 has a medium severity rating of 6.3 according to the CVSS score.

2

How do I fix CVE-2026-49740?

To fix CVE-2026-49740, ensure that you update TYPO3 CMS to the latest version where the vulnerability has been addressed.

3

What are the implications of CVE-2026-49740?

CVE-2026-49740 allows an attacker with write access to exploit insecure deserialization in TYPO3's cache frontend and key-value store.

4

Which TYPO3 versions are affected by CVE-2026-49740?

CVE-2026-49740 affects all versions of TYPO3 CMS that utilize the insecure deserialization in the core API.

5

Is there a known exploit for CVE-2026-49740?

As of now, there is no public knowledge of active exploits specifically targeting CVE-2026-49740.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203