How severe is GHSA-7vp9-x248-9vr9?

No CVSS score has been assigned to GHSA-7vp9-x248-9vr9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7vp9-x248-9vr9?

GHSA-7vp9-x248-9vr9 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-7vp9-x248-9vr9?

Update typo3/cms-core to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7vp9-x248-9vr9 is resolved across your whole dependency graph.

How do I detect GHSA-7vp9-x248-9vr9 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7vp9-x248-9vr9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7vp9-x248-9vr9?

O3 pinpoints whether GHSA-7vp9-x248-9vr9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7vp9-x248-9vr9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-7vp9-x248-9vr9 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 type of vulnerability is GHSA-7vp9-x248-9vr9?

GHSA-7vp9-x248-9vr9 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-7vp9-x248-9vr9 published, and has it been updated?

GHSA-7vp9-x248-9vr9 was published on January 13, 2026 and was last updated on February 3, 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

GHSA-7vp9-x248-9vr9

GHSA-7vp9-x248-9vr9 is a Deserialization of Untrusted Data vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-7vp9-x248-9vr9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TYPO3 CMS Allows Insecure Deserialization via Mailer File Spool

Also known asCVE-2026-0859

Published

Jan 13, 2026

Updated

Feb 3, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Blast Radius

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

Local platform users who can write to TYPO3’s mail‑file spool directory can craft a file that the system will automatically deserialize without any class restrictions. This flaw allows an attacker to inject and execute arbitrary PHP code in the public scope of the web server.

The vulnerability is triggered when TYPO3 is configured with $GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_type'] = 'file'; and a scheduler task or cron job runs the command mailer:spool:send. The spool‑send operation performs the insecure deserialization that is at the core of this issue.

Solution

Update to TYPO3 versions 10.4.55 ELTS, 11.5.49 ELTS, 12.4.41 LTS, 13.4.23 LTS, 14.0.2 that fix the problem described.

Credits

Thanks to Vitaly Simonovich for reporting this issue, and to TYPO3 security team members Elias Häußler and Oliver Hader for fixing it.

References

TYPO3-CORE-SA-2026-004

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 14.0.0&&< 14.0.2	14.0.2
🐘Packagist	`typo3/cms-core`	≥ 13.0.0&&< 13.4.23	13.4.23
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.4.41	12.4.41
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.49	11.5.49
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.55	10.4.55

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/cms-core to 14.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7vp9-x248-9vr9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7vp9-x248-9vr9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7vp9-x248-9vr9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem Local platform users who can write to TYPO3’s mail‑file spool directory can craft a file that the system will automatically deserialize without any class restrictions. This flaw allows an attacker to inject and execute arbitrary PHP code in the public scope of the web server. The vulnerability is triggered when TYPO3 is configured with `$GLOBALS['TYPO3_CONF_VARS']['MAIL']['transport_spool_type'] = 'file';` and a scheduler task or cron job runs the command `mailer:spool:send`. The spool‑send operation performs the insecure deserialization that is at the core of this issue. ### Sol

O3 Security · Impact-Aware SCA

Is GHSA-7vp9-x248-9vr9 in your dependencies?

O3 detects GHSA-7vp9-x248-9vr9 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works