symfony/validator vulnerabilities
Provides tools to validate values
- Registry
- Composer
- Latest
- 8.1.11
- License
- MIT
3 known advisories
The latest version, 8.1.11, is not affected by any of them. Projects on older versions may be.
composer require symfony/validator:^8.1.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
Security advisories for symfony/validator
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
symfony/validator XML Entity Expansion vulnerability
- Affected
- >=2.0.0 <2.0.17
- Fixed in
- 2.0.17
Symfony collectionCascaded and collectionCascadedDeeply fields security bypass
- Affected
- >=2.0.0 <2.0.24 · >=2.1.0 <2.1.12 · >=2.2.0 <2.2.5 · >=2.3.0 <2.3.3
- Fixed in
- 2.0.24, 2.1.12, 2.2.5, 2.3.3
Is your symfony/validator version vulnerable?
- symfony/validator 8.1No known advisories in 8.1.11
- symfony/validator 8.0No known advisories in 8.0.15
- symfony/validator 7.4No known advisories in 7.4.23
- symfony/validator 7.3No known advisories in 7.3.11
- symfony/validator 7.2No known advisories in 7.2.9
- symfony/validator 7.1No known advisories in 7.1.11
- symfony/validator 7.01 advisory in 7.0.10
- symfony/validator 6.4No known advisories in 6.4.50
- symfony/validator 6.31 advisory in 6.3.12
- symfony/validator 6.21 advisory in 6.2.13
- symfony/validator 6.11 advisory in 6.1.11
- symfony/validator 6.01 advisory in 6.0.19
Which of your client projects still run an old symfony/validator?
NPMscan reads the composer.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Composer packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Composer registry.