Is symfony/validator 7.1 vulnerable?

Composer · 12 releases from 7.1.0 to 7.1.11 · latest symfony/validator is 8.1.11 · checked 18 Nov 2026

No known advisories in the last release

symfony/validator 7.1.11, the last 7.1 release, has no known advisories. 1 advisory affects earlier 7.1.x releases, so update to 7.1.11.

Update within 7.1:composer require symfony/validator:^7.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

Fixed within 7.1.x, affecting earlier releases

  • 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

Every symfony/validator 7.1.x release

Affected: 7.1.0 to 7.1.3. 7.1.4 and later are not affected. Latest symfony/validator: 8.1.11.

VersionKnown advisories
symfony/validator 7.1.11None
symfony/validator 7.1.10None
symfony/validator 7.1.9None
symfony/validator 7.1.8None
symfony/validator 7.1.7None
symfony/validator 7.1.6None
symfony/validator 7.1.5None
symfony/validator 7.1.4None
symfony/validator 7.1.3CVE-2024-50343
symfony/validator 7.1.2CVE-2024-50343
symfony/validator 7.1.1CVE-2024-50343
symfony/validator 7.1.0CVE-2024-50343

Which of your client projects are still on symfony/validator 7.1?

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.