Vulnerability Database · Packagist · Package report

symfony/framework-bundle: vulnerability history, versions and safety

symfony/framework-bundle is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 63 releases, from Feb 2022 to May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on symfony/framework-bundle i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 30 May 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 2 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 30 May 2024 i
  • Highest CVSS 8.1 i
  • With no published fix 0 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/framework-bundle, 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
5.3.14 H1 Yes Details →
2.0.7 H1 Yes Details →
v5.3.14 H1 Yes Details →
v2.3.17 H1 Yes Details →
v2.3.16 H1 Yes Details →
v2.3.15 H1 Yes Details →
v2.3.14 H1 Yes Details →
v2.3.13 H1 Yes Details →
v2.3.12 H1 Yes Details →
v2.3.11 H1 Yes Details →
v2.3.10 H1 Yes Details →
v2.3.9 H1 Yes Details →
v2.3.8 H1 Yes Details →
v2.3.7 H1 Yes Details →
v2.3.6 H1 Yes Details →
v2.3.5 H1 Yes Details →
v2.3.4 H1 Yes Details →
v2.3.3 H1 Yes Details →
v2.3.2 H1 Yes Details →
v2.3.1 H1 Yes Details →
v2.3.0 H1 Yes Details →
v2.2.11 H1 Yes Details →
v2.2.10 H1 Yes Details →
v2.2.9 H1 Yes Details →
v2.2.8 H1 Yes Details →
v2.2.7 H1 Yes Details →
v2.2.6 H1 Yes Details →
v2.2.5 H1 Yes Details →
v2.2.4 H1 Yes Details →
v2.2.3 H1 Yes Details →
v2.2.2 H1 Yes Details →
v2.2.1 H1 Yes Details →
v2.2.0 H1 Yes Details →
v2.1.13 H1 Yes Details →
v2.1.12 H1 Yes Details →
v2.1.11 H1 Yes Details →
v2.1.10 H1 Yes Details →
v2.1.9 H1 Yes Details →
v2.1.8 H1 Yes Details →
v2.1.7 H1 Yes Details →
v2.1.6 H1 Yes Details →
v2.1.5 H1 Yes Details →
v2.1.4 H1 Yes Details →
v2.1.3 H1 Yes Details →
v2.1.2 H1 Yes Details →
v2.1.1 H1 Yes Details →
v2.1.0 H1 Yes Details →
v2.0.25 H1 Yes Details →
v2.0.24 H1 Yes Details →
v2.0.23 H1 Yes Details →
v2.0.22 H1 Yes Details →
v2.0.21 H1 Yes Details →
v2.0.20 H1 Yes Details →
v2.0.19 H1 Yes Details →
v2.0.18 H1 Yes Details →
v2.0.17 H1 Yes Details →
v2.0.16 H1 Yes Details →
v2.0.15 H1 Yes Details →
v2.0.14 H1 Yes Details →
v2.0.13 H1 Yes Details →
v2.0.12 H1 Yes Details →
v2.0.10 H1 Yes Details →
v2.0.9 H1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for symfony/framework-bundle

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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/framework-bundle

Is symfony/framework-bundle safe to use?

Vulert records 2 vulnerabilities for symfony/framework-bundle in Packagist: 0 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does symfony/framework-bundle have?

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

How often are new symfony/framework-bundle vulnerabilities disclosed?

0 vulnerabilities were recorded for symfony/framework-bundle in the last 12 months, and the oldest entry in this database dates to 01 Feb 2022. 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/framework-bundle 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/framework-bundle for upcoming vulnerabilities?

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