No. Junglewise Threat Intelligence has no report of CVE-2019-10912 being exploited in the wild.
How severe is CVE-2019-10912?
Low severity, with a CVSS score of 3, published 12 February 2020.
Which products and versions are affected?
symfony/cache (Packagist) ECOSYSTEM:introduced=3.1.0,fixed=3.4.26; symfony/phpunit-bridge (Packagist) ECOSYSTEM:introduced=2.8.0,fixed=2.8.50; symfony/symfony (Packagist) ECOSYSTEM:introduced=2.8.0,fixed=2.8.50; typo3/cms (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=9.5.8; and 1 more.
Is there a fix for CVE-2019-10912?
Yes. symfony/cache (Packagist): upgrade to 3.4.26 or later; symfony/phpunit-bridge (Packagist): upgrade to 2.8.50 or later; symfony/symfony (Packagist): upgrade to 2.8.50 or later; typo3/cms (Packagist): upgrade to 9.5.8 or later; typo3/cms-core (Packagist): upgrade to 9.5.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-10912?
Check whether you run symfony/cache (Packagist), symfony/phpunit-bridge (Packagist), symfony/symfony (Packagist) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
symfony/cache (Packagist): upgrade to 3.4.26 or later
composer require symfony/cache:^3.4.26
symfony/phpunit-bridge (Packagist): upgrade to 2.8.50 or later
composer require symfony/phpunit-bridge:^2.8.50
symfony/symfony (Packagist): upgrade to 2.8.50 or later
composer require symfony/symfony:^2.8.50
typo3/cms (Packagist): upgrade to 9.5.8 or later
composer require typo3/cms:^9.5.8
typo3/cms-core (Packagist): upgrade to 9.5.8 or later