cve.bz

CVE-2026-49740 typo3 typo3 cms: Deserialization of Untrusted Data

6.3 mediumEPSS 0.2%Fix available

Medium (6.3) in typo3 typo3 cms. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in typo3/cms-core 10.4.57, 11.5.51, 12.4.46.

On this page
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.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.

Severity

CVSS 4.0

6.3 medium
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
EPSS
0.2% (unchanged from 0.2% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • typo3/cms-core (Packagist): fixed in 10.4.57, 11.5.51, 12.4.46, 13.4.31, 14.3.3

Ask an AI about this CVE

Show the promptExplain CVE-2026-49740 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49740?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49740?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49740 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
TYPO3 CMSbefore 10.4.57
TYPO3 CMSfrom 11.0.0 before 11.5.51
TYPO3 CMSfrom 12.0.0 before 12.4.46
TYPO3 CMSfrom 13.0.0 before 13.4.31
TYPO3 CMSfrom 14.0.0 before 14.3.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-c78m-c52x-jgwpPackagisttypo3/cms-core<10.4.5710.4.57
GHSA-c78m-c52x-jgwpPackagisttypo3/cms-core>=11.0.0 <11.5.5111.5.51
GHSA-c78m-c52x-jgwpPackagisttypo3/cms-core>=12.0.0 <12.4.4612.4.46
GHSA-c78m-c52x-jgwpPackagisttypo3/cms-core>=13.0.0 <13.4.3113.4.31
GHSA-c78m-c52x-jgwpPackagisttypo3/cms-core>=14.0.0 <14.3.314.3.3

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON