How severe is CVE-2019-10912?

CVE-2019-10912 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-10912?

CVE-2019-10912 affects the following packages: symfony/cache (Packagist), symfony/cache (Packagist), symfony/cache (Packagist), symfony/phpunit-bridge (Packagist), symfony/phpunit-bridge (Packagist), symfony/phpunit-bridge (Packagist), symfony/phpunit-bridge (Packagist), symfony/symfony (Packagist), and 5 more. Ecosystems affected: Packagist.

How do I fix CVE-2019-10912?

Update symfony/cache to 3.4.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10912 is resolved across your whole dependency graph.

How do I detect CVE-2019-10912 in my Packagist dependencies?

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

How do I mitigate CVE-2019-10912 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 CVE-2019-10912 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-10912 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 CVE-2019-10912?

CVE-2019-10912 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 82th 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 CVE-2019-10912?

CVE-2019-10912 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 CVE-2019-10912 published, and has it been updated?

CVE-2019-10912 was published on May 16, 2019 and was last updated on August 7, 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

HIGH severity

CVE-2019-10912 — cache

HIGHFix: symfony/symfony@4fb9752

CVE-2019-10912 is a high-severity (CVSS 7.1) Deserialization of Untrusted Data vulnerability in symfony/cache. A fix is available for symfony/cache — see the affected versions and patch details below.

Deserialization of untrusted data in Symfony

Also known asGHSA-w2fr-65vp-mxw3

Published

May 16, 2019

Updated

Aug 7, 2026

Affected

13 pkgs

Patched

13 / 13

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

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

How urgent is this, really

CVE-2019-10912 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,534 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

13 pkgs affected

🐘symfony/cache🐘symfony/cache🐘symfony/cache🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/symfony+5 more

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

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.

Affected Packages

13 total 13 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/cache`	≥ 3.1.0&&< 3.4.26	3.4.26`composer require symfony/cache:^3.4.26`
🐘Packagist	`symfony/cache`	≥ 4.0.0&&< 4.1.12	4.1.12`composer require symfony/cache:^4.1.12`
🐘Packagist	`symfony/cache`	≥ 4.2.0&&< 4.2.7	4.2.7`composer require symfony/cache:^4.2.7`
🐘Packagist	`symfony/phpunit-bridge`	≥ 2.8.0&&< 2.8.50	2.8.50`composer require symfony/phpunit-bridge:^2.8.50`
🐘Packagist	`symfony/phpunit-bridge`	≥ 3.0.0&&< 3.4.26	3.4.26`composer require symfony/phpunit-bridge:^3.4.26`
🐘Packagist	`symfony/phpunit-bridge`	≥ 4.0.0&&< 4.1.12	4.1.12`composer require symfony/phpunit-bridge:^4.1.12`

Affected Products

1 product · 4 configurations

Application

symfonysensiolabs

≥ 4.2.0 && < 4.2.7

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/cache, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/cache to 3.4.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-10912 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

O3 Security · Impact-Aware SCA

Is CVE-2019-10912 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works