Loading...
Skip to main content
GeekWala

CVE-2026-49740 — Vulnerability in typo3/cms-core — CVE Details

MEDIUM

TYPO3 CMS has Insecure Deserialization via Core API

Published June 12, 2026Updated September 10, 2026Source: osv

Summary

### 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](https://typo3.org/security/advisory/typo3-core-sa-2026-018)

Advisory Timeline

  • First published June 12, 2026 (122 days ago).
  • Last revised September 10, 2026 — 89 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Composer
Update typo3/cms-core to 13.4.31 or later
composer require "typo3/cms-core:^13.4.31"
Composer
Update typo3/cms-core to 11.5.51 or later
composer require "typo3/cms-core:^11.5.51"
Composer
Update typo3/cms-core to 12.4.46 or later
composer require "typo3/cms-core:^12.4.46"
Composer
Update typo3/cms-core to 10.4.57 or later
composer require "typo3/cms-core:^10.4.57"
Composer
Update typo3/cms-core to 14.3.3 or later
composer require "typo3/cms-core:^14.3.3"

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (5)

Affects 1 ecosystem: packagist (1).

PackageEcosystemAffectedFixed In
typo3/cms-core
packagist
v13.0.0, v13.0.1, v13.1.0, v13.1.1 (+35 more)13.4.31
typo3/cms-core
packagist
v11.0.0, v11.1.0, v11.1.1, v11.2.0 (+47 more)11.5.51
typo3/cms-core
packagist
v12.0.0, v12.1.0, v12.1.1, v12.1.2 (+49 more)12.4.46
typo3/cms-core
packagist
v10.0.0, v10.1.0, v10.2.0, v10.2.1 (+106 more)10.4.57
typo3/cms-core
packagist
v14.0.0, v14.0.1, v14.0.2, v14.1.0 (+5 more)14.3.3

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

  • CWE-502
    Deserialization of Untrusted DataMITRE

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.8 score means for each attack dimension.

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

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

References

Frequently Asked Questions

What is CVE-2026-49740?
TYPO3 CMS has Insecure Deserialization via Core API This vulnerability has been assigned a severity rating of MEDIUM (CVSS score: 8.8/10).
How do I check if my project is affected by CVE-2026-49740?
CVE-2026-49740 affects typo3/cms-core. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-49740 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.8

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-c78m-c52x-jgwp

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies