Composer symfony/dependency-injection has 3 known advisories in the phpwarden feed. Feed 2026.10.28.3, updated 2026-10-28.
| CVE | Title | Severity | CVSS | Affected | Fixed in |
|---|---|---|---|---|---|
| CVE-2019-10910 | Symfony Service IDs Allow Injection | critical | 9.8 | >=2.7.0 and <2.7.51 or >=2.8.0 and <2.8.50 or >=3.0.0 and <3.4.26 or >=4.0.0 and <4.1.12 or >=4.2.0 and <4.2.7 or >=3.0.0 and <3.1.0 or >=3.1.0 and <3.2.0 or >=3.2.0 and <3.3.0 or >=3.3.0 and <3.4.0 or >=3.4.0 and <3.4.26 or >=4.0.0 and <4.1.0 or >=4.1.0 and <4.1.12 | 2.7.51, 2.8.50, 3.4.26, 4.1.12 |
| GHSA-c636-cg5r-2498 | Symfony XML Entity Expansion security vulnerability | high | 7.5 | >=2.0.0 and <2.0.17 | 2.0.17 |
| 2012-08-28 | Security fixes related to the way XML is handled | unknown | 0.0 | >=2.0.0 and <2.0.17 | 2.0.17 |
Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.
# one-time install pip install phpwarden # then phpwarden deps composer.lock
Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command
Install docs How findings are ranked