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.

Update to the latest version:composer require symfony/validator:^8.1.11

Is your project on an affected symfony/validator?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • LowCVE-2024-50343GHSA-g3rh-rrhp-jhh96 Nov 2024

    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
  • HighGHSA-4vf2-qfg3-759830 May 2024

    symfony/validator XML Entity Expansion vulnerability

    Affected
    >=2.0.0 <2.0.17
    Fixed in
    2.0.17
  • HighCVE-2013-4751GHSA-q8j7-fjh7-25v55 May 2022

    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?

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.