GHSA-w2fr-65vp-mxw3 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.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-w2fr-65vp-mxw3 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
symfony/cache🐘symfony/cache🐘symfony/cache🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/phpunit-bridge🐘symfony/symfony+5 moreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/cache | ≥ 3.1.0&&< 3.4.26 | 3.4.26composer require symfony/cache:^3.4.26 |
| 🐘Packagist | symfony/cache | ≥ 4.0.0&&< 4.1.12 | 4.1.12composer require symfony/cache:^4.1.12 |
| 🐘Packagist | symfony/cache | ≥ 4.2.0&&< 4.2.7 | 4.2.7composer require symfony/cache:^4.2.7 |
| 🐘Packagist | symfony/phpunit-bridge | ≥ 2.8.0&&< 2.8.50 | 2.8.50composer require symfony/phpunit-bridge:^2.8.50 |
| 🐘Packagist | symfony/phpunit-bridge | ≥ 3.0.0&&< 3.4.26 | 3.4.26composer require symfony/phpunit-bridge:^3.4.26 |
| 🐘Packagist | symfony/phpunit-bridge | ≥ 4.0.0&&< 4.1.12 | 4.1.12composer require symfony/phpunit-bridge:^4.1.12 |
Affected Products
symfonysensiolabsDetection & mitigation playbook
Open-source dependencyDetect
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 GHSA-w2fr-65vp-mxw3 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
Is GHSA-w2fr-65vp-mxw3 in your dependencies?
Find it across Packagist, including transitive dependencies.