Is symfony/validator 6.2 vulnerable?
Composer · 10 releases from 6.2.0 to 6.2.13 · latest symfony/validator is 8.1.11 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. symfony/validator 6.2.13, the last 6.2 release, is affected by 1 known security advisory (1 low), including CVE-2024-50343. Upgrade to 6.4.11 or later to fix all of them.
composer require symfony/validator:^6.4.11Is your project on an affected symfony/validator?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting symfony/validator 6.2.13
Symfony has an incorrect response from Validator when input ends with `\n`
- Affected
- <5.4.43 · >=6.0.0 <6.4.11 · >=7.0.0 <7.1.4
- Fixed in
- 5.4.43, 6.4.11, 7.1.4
Every symfony/validator 6.2.x release
Affected: 6.2.0 to 6.2.13. Latest symfony/validator: 8.1.11.
| Version | Known advisories |
|---|---|
| symfony/validator 6.2.13 | CVE-2024-50343 |
| symfony/validator 6.2.12 | CVE-2024-50343 |
| symfony/validator 6.2.11 | CVE-2024-50343 |
| symfony/validator 6.2.10 | CVE-2024-50343 |
| symfony/validator 6.2.8 | CVE-2024-50343 |
| symfony/validator 6.2.7 | CVE-2024-50343 |
| symfony/validator 6.2.5 | CVE-2024-50343 |
| symfony/validator 6.2.3 | CVE-2024-50343 |
| symfony/validator 6.2.2 | CVE-2024-50343 |
| symfony/validator 6.2.0 | CVE-2024-50343 |
Which of your client projects are still on symfony/validator 6.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact symfony/validator version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other symfony/validator versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.