Vulnerability Database · Packagist · Package report

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

symfony/security-bundle is a package in the Packagist ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Nov 2021 to Nov 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M2 L1
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/security-bundle i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 3 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 3 over 2 years · 0 in the last year i
  • Latest disclosure 06 Nov 2024 i
  • Highest CVSS 6.5 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/security-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
2.0.7 M1 Yes Details →
v6.4.9 L1 Yes Details →
v6.4.8 L1 Yes Details →
v6.4.7 L1 Yes Details →
v6.4.6 L1 Yes Details →
v6.4.5 L1 Yes Details →
v6.4.4 L1 Yes Details →
v6.4.3 L1 Yes Details →
v6.4.2 L1 Yes Details →
v6.4.0 L1 Yes Details →
v6.4.0-RC1 L1 Yes Details →
v6.4.0-BETA3 L1 Yes Details →
v6.4.0-BETA2 L1 Yes Details →
v6.4.0-BETA1 L1 Yes Details →
v6.3.12 L1 Yes Details →
v6.3.11 L1 Yes Details →
v6.3.8 L1 Yes Details →
v6.3.7 L1 Yes Details →
v6.3.6 L1 Yes Details →
v6.3.5 L1 Yes Details →
v6.3.4 L1 Yes Details →
v6.3.3 L1 Yes Details →
v6.3.2 L1 Yes Details →
v6.3.1 L1 Yes Details →
v6.3.0 L1 Yes Details →
v6.3.0-RC2 L1 Yes Details →
v6.3.0-RC1 L1 Yes Details →
v6.3.0-BETA2 L1 Yes Details →
v6.3.0-BETA1 L1 Yes Details →
v6.2.13 L1 Yes Details →
v6.2.12 L1 Yes Details →
v6.2.11 L1 Yes Details →
v6.2.10 L1 Yes Details →
v6.2.8 L1 Yes Details →
v6.2.7 L1 Yes Details →
v6.2.6 L1 Yes Details →
v6.2.5 L1 Yes Details →
v6.2.3 L1 Yes Details →
v6.2.2 L1 Yes Details →
v6.2.0 L1 Yes Details →
v5.3.11 M1 Yes Details →
v5.3.8 M1 Yes Details →
v5.3.7 M1 Yes Details →
v5.3.4 M1 Yes Details →
v5.3.3 M1 Yes Details →
v5.3.2 M1 Yes Details →
v5.3.0 M1 Yes Details →
v4.4.44 M1 Yes Details →
v4.4.42 M1 Yes Details →
v4.4.41 M1 Yes Details →
v4.4.38 M1 Yes Details →
v4.4.37 M1 Yes Details →
v4.4.36 M1 Yes Details →
v4.4.34 M1 Yes Details →
v4.4.27 M1 Yes Details →
v4.4.26 M1 Yes Details →
v4.4.25 M1 Yes Details →
v4.4.23 M1 Yes Details →
v4.4.22 M1 Yes Details →
v4.4.21 M1 Yes Details →
v4.4.20 M1 Yes Details →
v4.4.19 M1 Yes Details →
v4.4.18 M1 Yes Details →
v4.4.17 M1 Yes Details →
v4.4.16 M1 Yes Details →
v4.4.15 M1 Yes Details →
v4.4.14 M1 Yes Details →
v4.4.13 M1 Yes Details →
v4.4.12 M1 Yes Details →
v4.4.11 M1 Yes Details →
v4.4.10 M1 Yes Details →
v4.4.9 M1 Yes Details →
v4.4.8 M1 Yes Details →
v4.4.7 M1 Yes Details →
v4.4.6 M1 Yes Details →
v4.4.5 M1 Yes Details →
v4.4.4 M1 Yes Details →
v4.4.3 M1 Yes Details →
v4.4.2 M1 Yes Details →
v4.4.1 M1 Yes Details →
v4.4.0 M1 Yes Details →
v4.4.0-RC1 M1 Yes Details →
v4.4.0-BETA2 M1 Yes Details →
v4.4.0-BETA1 M1 Yes Details →
v4.3.11 M1 Yes Details →
v4.3.10 M1 Yes Details →
v4.3.9 M1 Yes Details →
v4.3.8 M1 Yes Details →
v4.3.7 M1 Yes Details →
v4.3.6 M1 Yes Details →
v4.3.5 M1 Yes Details →
v4.3.4 M1 Yes Details →
v4.3.3 M1 Yes Details →
v4.3.2 M1 Yes Details →
v4.3.1 M1 Yes Details →
v4.3.0 M1 Yes Details →
v4.3.0-RC1 M1 Yes Details →
v4.3.0-BETA2 M1 Yes Details →
v4.3.0-BETA1 M1 Yes Details →
v4.2.12 M1 Yes Details →
v4.2.11 M1 Yes Details →
v4.2.10 M1 Yes Details →
v4.2.9 M1 Yes Details →
v4.2.8 M1 Yes Details →
v4.2.7 M1 Yes Details →
v4.2.6 M1 Yes Details →
v4.2.5 M1 Yes Details →
v4.2.4 M1 Yes Details →
v4.2.3 M1 Yes Details →
v4.2.2 M1 Yes Details →
v4.2.1 M1 Yes Details →
v4.2.0 M1 Yes Details →
v4.2.0-RC1 M1 Yes Details →
v4.2.0-BETA2 M1 Yes Details →
v4.2.0-BETA1 M1 Yes Details →
v4.1.12 M1 Yes Details →
v4.1.11 M1 Yes Details →
v4.1.10 M1 Yes Details →
v4.1.9 M1 Yes Details →
v4.1.8 M1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2023 1
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for symfony/security-bundle

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 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/security-bundle

Is symfony/security-bundle safe to use?

Vulert records 3 vulnerabilities for symfony/security-bundle in Packagist: 0 critical, 0 high, 2 medium and 1 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/security-bundle have?

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

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the symfony/security-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.