Vulnerability Database · Packagist · Package report

symfony/symfony: vulnerability history, versions and safety

symfony/symfony is a package in the Packagist ecosystem. Vulert records 25 vulnerabilities for it across 120 releases, from Nov 2019 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
25 vulnerabilities recorded C2 H8 M12 L3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 29 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on symfony/symfony i

Updated on 23 Oct 2026

Careful: one of the 25 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 25 vulnerabilities on record across 6 years, 2 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 25 over 6 years · 2 in the last year i
  • Latest disclosure 29 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for symfony/symfony, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.2-dev M1 No Details →
2.0.7 C1 H3 M4 L1 Yes Details →
2.0.6 C1 H3 M4 L1 Yes Details →
2.0.5 C1 H3 M5 L1 Yes Details →
2.0.4 C1 H3 M5 L1 Yes Details →
v6.4.39 M1 L1 Yes Details →
v6.4.38 M1 L1 Yes Details →
v6.4.37 M1 L1 Yes Details →
v6.4.36 M1 L1 Yes Details →
v6.4.35 M1 L1 Yes Details →
v6.4.34 M1 L1 Yes Details →
v6.4.33 M1 L1 Yes Details →
v6.4.32 M1 L1 Yes Details →
v6.4.31 M1 L1 Yes Details →
v6.4.30 M1 L1 Yes Details →
v6.4.29 M1 L1 Yes Details →
v6.4.28 M1 L1 Yes Details →
v6.4.27 M1 L1 Yes Details →
v6.4.26 M1 L1 Yes Details →
v6.4.25 M1 L1 Yes Details →
v6.4.24 M1 L1 Yes Details →
v6.4.23 M1 Yes Details →
v6.4.22 M1 Yes Details →
v6.4.21 M1 Yes Details →
v6.4.20 M1 Yes Details →
v6.4.19 M1 Yes Details →
v6.4.18 M1 Yes Details →
v6.4.17 M1 Yes Details →
v6.4.16 M1 Yes Details →
v6.4.15 M1 Yes Details →
v6.4.14 M1 Yes Details →
v6.4.13 M1 Yes Details →
v6.4.12 M1 Yes Details →
v6.4.11 M1 Yes Details →
v6.4.10 M1 Yes Details →
v6.4.9 M1 Yes Details →
v6.4.8 M1 Yes Details →
v6.4.7 M1 Yes Details →
v6.4.6 M1 Yes Details →
v6.4.5 M1 Yes Details →
v6.4.4 M1 Yes Details →
v6.4.3 M1 Yes Details →
v6.4.2 M1 Yes Details →
v6.4.1 M1 Yes Details →
v6.4.0 M1 Yes Details →
v5.4.42 L1 Yes Details →
v5.4.41 L1 Yes Details →
v5.4.40 L1 Yes Details →
v5.4.39 L1 Yes Details →
v5.4.38 L1 Yes Details →
v5.4.37 L1 Yes Details →
v5.4.36 L1 Yes Details →
v5.4.35 L1 Yes Details →
v5.4.34 L1 Yes Details →
v5.4.33 L1 Yes Details →
v5.4.32 L1 Yes Details →
v5.4.31 L1 Yes Details →
v5.4.30 L1 Yes Details →
v5.4.29 L1 Yes Details →
v5.4.28 L1 Yes Details →
v5.4.27 L1 Yes Details →
v5.4.26 L1 Yes Details →
v5.4.25 L1 Yes Details →
v5.4.24 L1 Yes Details →
v5.4.23 L1 Yes Details →
v5.4.22 L1 Yes Details →
v5.4.21 L1 Yes Details →
v5.4.20 L1 Yes Details →
v5.4.19 L1 Yes Details →
v5.4.18 L1 Yes Details →
v5.4.17 L1 Yes Details →
v5.4.16 L1 Yes Details →
v5.4.15 L1 Yes Details →
v5.4.14 L1 Yes Details →
v5.4.13 L1 Yes Details →
v5.4.12 L1 Yes Details →
v5.4.11 L1 Yes Details →
v5.4.10 L1 Yes Details →
v5.4.9 L1 Yes Details →
v5.4.8 L1 Yes Details →
v5.4.7 L1 Yes Details →
v5.4.6 L1 Yes Details →
v5.4.5 L1 Yes Details →
v5.4.4 L1 Yes Details →
v5.4.3 L1 Yes Details →
v5.4.2 L1 Yes Details →
v5.4.1 L1 Yes Details →
v5.4.0 L1 Yes Details →
v5.4.0-RC1 L1 Yes Details →
v5.4.0-BETA3 L1 Yes Details →
v5.4.0-BETA2 L1 Yes Details →
v5.4.0-BETA1 L1 Yes Details →
v5.3.16 L1 Yes Details →
v5.3.15 L1 Yes Details →
v5.3.14 L1 Yes Details →
v5.3.13 L1 Yes Details →
v5.3.12 L1 Yes Details →
v5.3.11 L1 Yes Details →
v5.3.10 L1 Yes Details →
v5.3.9 L1 Yes Details →
v5.3.8 L1 Yes Details →
v5.3.7 L1 Yes Details →
v5.3.6 L1 Yes Details →
v5.3.5 L1 Yes Details →
v5.3.4 L1 Yes Details →
v5.3.3 L1 Yes Details →
v5.3.2 L1 Yes Details →
v5.3.1 L1 Yes Details →
v5.3.0 L1 Yes Details →
v5.3.0-RC1 L1 Yes Details →
v5.3.0-BETA4 L1 Yes Details →
v5.3.0-BETA3 L1 Yes Details →
v5.3.0-BETA2 L1 Yes Details →
v5.3.0-BETA1 L1 Yes Details →
v5.2.14 L1 Yes Details →
v5.2.13 L1 Yes Details →
v5.2.12 L1 Yes Details →
v5.2.11 L1 Yes Details →
v5.2.10 L1 Yes Details →
v5.2.9 L1 Yes Details →

Newest 120 of 663 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1
  • 2022 15
  • 2024 6
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 25 were recorded in the last 12 months.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About symfony/symfony

Is symfony/symfony safe to use?

Vulert records 25 vulnerabilities for symfony/symfony in Packagist: 2 critical, 8 high, 12 medium and 3 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does symfony/symfony have?

25 vulnerabilities are recorded for symfony/symfony in the Packagist ecosystem: 2 critical, 8 high, 12 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new symfony/symfony vulnerabilities disclosed?

2 vulnerabilities were recorded for symfony/symfony in the last 12 months, and the oldest entry in this database dates to 12 Nov 2019. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of symfony/symfony are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor symfony/symfony for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the symfony/symfony version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.