Unsafe Deserialization in typo3/cms-core (CVE-2026-49740)
Summary
Vulnerability in typo3/cms-core (CVE-2026-49740). Risk of unauthorized operations or information disclosure. Exploitable via VariableFrontend. Mitigation: upgrade to 14.3.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49740 has been found in typo3/cms-core.
Attackers can target a specific entry point like VariableFrontend over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade typo3/cms-core to 14.3.3 or later.
If unsure, ask your IT team or search "typo3/cms-core CVE-2026-49740" on the vendor's site.
CVE-2026-49740 (typo3/cms-core) — CWE-502
Attack surface: VariableFrontend / Registry
Patched: 14.3.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in typo3/cms-core. Attackers reach the vulnerable code path via VariableFrontend.
Check the vendor advisory for the affected versions of typo3/cms-core. Attack surface: VariableFrontend / Registry.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 14.3.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'typo3/cms-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'typo3/cms-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
typo3/cms-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade typo3/cms-core to 14.3.3ステージング環境で 14.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory typo3.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com
- web packagist.org