How severe is GHSA-c78m-c52x-jgwp?

No CVSS score has been assigned to GHSA-c78m-c52x-jgwp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c78m-c52x-jgwp?

GHSA-c78m-c52x-jgwp affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c78m-c52x-jgwp?

Update typo3/cms-core to 10.4.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c78m-c52x-jgwp is resolved across your whole dependency graph.

How do I detect GHSA-c78m-c52x-jgwp in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-c78m-c52x-jgwp if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-c78m-c52x-jgwp actively exploited in the wild?

No public exploit code has been indexed for GHSA-c78m-c52x-jgwp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c78m-c52x-jgwp?

GHSA-c78m-c52x-jgwp has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c78m-c52x-jgwp?

GHSA-c78m-c52x-jgwp is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c78m-c52x-jgwp published, and has it been updated?

GHSA-c78m-c52x-jgwp was published on June 12, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

TYPO3 CMS has Insecure Deserialization via Core APIGHSA-c78m-c52x-jgwp

Fix: TYPO3/typo3@48bcf24

GHSA-c78m-c52x-jgwp is a Deserialization of Untrusted Data vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asCVE-2026-49740

Published

Jun 12, 2026

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c78m-c52x-jgwp.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	all versions	10.4.57`composer require typo3/cms-core:^10.4.57`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.51	11.5.51`composer require typo3/cms-core:^11.5.51`
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.4.46	12.4.46`composer require typo3/cms-core:^12.4.46`
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.31	13.4.31`composer require typo3/cms-core:^13.4.31`
🐘Packagist	`typo3/cms-core`	≥ 14.0.0&&< 14.3.3	14.3.3`composer require typo3/cms-core:^14.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 10.4.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c78m-c52x-jgwp is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-c78m-c52x-jgwp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works