CVE-2019-10912

In Symfony before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, it is possible to cache objects that may contain bad user input. On serialization or unserialization, this could result in the deletion of files that the current user has access to. This is related to symfony/cache and symfony/phpunit-bridge.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2019-10912 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.4.26, 4.1.12, 4.2.7, 2.8.50, 9.5.8); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2019-10912? CVE-2019-10912 is a high-severity insecure deserialization vulnerability in symfony/cache (composer), affecting versions >= 3.1.0, < 3.4.26. It is fixed in 3.4.26, 4.1.12, 4.2.7, 2.8.50, 9.5.8. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2019-10912? CVE-2019-10912 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2019-10912?
   • symfony/cache (composer) (versions >= 3.1.0, < 3.4.26)
   • symfony/phpunit-bridge (composer) (versions >= 2.8.0, < 2.8.50)
   • symfony/symfony (composer) (versions >= 2.8.0, < 2.8.50)
   • typo3/cms-core (composer) (versions >= 9.0.0, < 9.5.8)
   • typo3/cms (composer) (versions >= 9.0.0, < 9.5.8)
4. Is there a fix for CVE-2019-10912? Yes. CVE-2019-10912 is fixed in 3.4.26, 4.1.12, 4.2.7, 2.8.50, 9.5.8. Upgrade to this version or later.
5. Is CVE-2019-10912 exploitable, and should I be worried? Whether CVE-2019-10912 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2019-10912 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2019-10912?
   • Upgrade symfony/cache to 3.4.26 or later
   • Upgrade symfony/cache to 4.1.12 or later
   • Upgrade symfony/cache to 4.2.7 or later
   • Upgrade symfony/phpunit-bridge to 2.8.50 or later
   • Upgrade symfony/phpunit-bridge to 3.4.26 or later
   • Upgrade symfony/phpunit-bridge to 4.1.12 or later
   • Upgrade symfony/phpunit-bridge to 4.2.7 or later
   • Upgrade symfony/symfony to 2.8.50 or later
   • Upgrade symfony/symfony to 3.4.26 or later
   • Upgrade symfony/symfony to 4.1.12 or later
   • Upgrade symfony/symfony to 4.2.7 or later
   • Upgrade typo3/cms-core to 9.5.8 or later
   • Upgrade typo3/cms to 9.5.8 or later