HighGHSA-86hp-xrhj-fhpqCVE-2019-12747
TYPO3 Vulnerable to Insecure Deserialization
Published 24 May 2022 · Updated 3 Feb 2026
Affected packages
typo3/cms-coreComposer
- Affected
- >=8.0.0 <8.7.27
- Fixed in
- 8.7.27
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^8.7.27typo3/cms-coreComposer
- Affected
- >=9.0.0 <9.5.8
- Fixed in
- 9.5.8
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^9.5.8typo3/cmsComposer
- Affected
- >=8.0.0 <8.7.27
- Fixed in
- 8.7.27
Update to the fixed version for your release line, for example:
composer require typo3/cms:^8.7.27typo3/cmsComposer
- Affected
- >=9.0.0 <9.5.8
- Fixed in
- 9.5.8
Update to the fixed version for your release line, for example:
composer require typo3/cms:^9.5.8Details
TYPO3 8.x through 8.7.26 and 9.x through 9.5.7 allows Deserialization of Untrusted Data.
Is GHSA-86hp-xrhj-fhpq in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2019-12747
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2019-12747.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2019-12747.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/cms/release-news/typo3-8-release-notes
- Linktypo3.org/security/advisory/typo3-core-sa-2019-020
- Linkgithub.com/TYPO3/typo3/commit/647aa7afa582983cddc547fa106d31e2b1ef34fe
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.