Vulnerability Database · Packagist · Package report

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

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

i
13 vulnerabilities recorded H5 M7 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 15 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on symfony/security-http i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 13 vulnerabilities on record across 6 years, 4 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 13 over 6 years · 4 in the last year i
  • Latest disclosure 15 Jun 2026 i
  • Highest CVSS 8.7 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-http, 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
v7.4.11 M1 Yes Details →
v7.4.9 M1 Yes Details →
v7.4.8 M1 Yes Details →
v7.4.6 M1 Yes Details →
v7.4.4 M1 Yes Details →
v7.4.3 M1 Yes Details →
v7.4.1 M1 Yes Details →
v7.4.0 M1 Yes Details →
v7.4.0-RC2 M1 Yes Details →
v7.4.0-RC1 M1 Yes Details →
v7.4.0-BETA1 M1 Yes Details →
v7.3.10 M1 Yes Details →
v7.3.9 M1 Yes Details →
v7.3.8 M1 Yes Details →
v7.3.5 M1 Yes Details →
v7.3.4 M1 Yes Details →
v7.3.3 M1 Yes Details →
v7.3.2 M1 Yes Details →
v7.3.1 M1 Yes Details →
v7.3.0 M1 Yes Details →
v7.3.0-RC1 M1 Yes Details →
v7.3.0-BETA2 M1 Yes Details →
v7.3.0-BETA1 M1 Yes Details →
v7.2.9 M1 Yes Details →
v7.2.8 M1 Yes Details →
v7.2.7 M1 Yes Details →
v7.2.6 M1 Yes Details →
v7.2.4 M1 Yes Details →
v7.2.3 M1 Yes Details →
v7.2.1 M1 Yes Details →
v7.2.0 M1 Yes Details →
v7.2.0-RC1 M1 Yes Details →
v7.2.0-BETA2 M1 Yes Details →
v7.2.0-BETA1 M1 Yes Details →
v7.1.11 M1 Yes Details →
v7.1.10 M1 Yes Details →
v7.1.8 M1 Yes Details →
v7.1.7 M1 Yes Details →
v7.1.6 M1 Yes Details →
v7.1.5 M1 Yes Details →
v7.1.4 M1 Yes Details →
v7.1.3 M1 Yes Details →
v7.1.2 M1 Yes Details →
v7.1.1 M1 Yes Details →
v7.1.0 M1 Yes Details →
v7.1.0-RC1 M1 Yes Details →
v7.1.0-BETA1 M1 Yes Details →
v7.0.9 M1 Yes Details →
v7.0.8 M1 Yes Details →
v7.0.7 M1 Yes Details →
v7.0.4 M1 Yes Details →
v7.0.3 M1 Yes Details →
v7.0.1 M1 Yes Details →
v7.0.0 M1 Yes Details →
v7.0.0-RC2 M1 Yes Details →
v7.0.0-RC1 M1 Yes Details →
v7.0.0-BETA3 M1 Yes Details →
v7.0.0-BETA1 M1 Yes Details →
v6.4.39 M1 Yes Details →
v6.4.34 M1 Yes Details →
v6.4.31 M1 Yes Details →
v6.4.30 M1 Yes Details →
v6.4.26 M1 Yes Details →
v6.4.25 M1 Yes Details →
v6.4.24 M1 Yes Details →
v6.4.23 M1 Yes Details →
v6.4.22 M1 Yes Details →
v6.4.21 M1 Yes Details →
v6.4.19 M1 Yes Details →
v6.4.18 M1 Yes Details →
v6.4.15 M2 Yes Details →
v6.4.14 M2 Yes Details →
v6.4.13 M2 Yes Details →
v6.4.12 M2 Yes Details →
v6.4.11 M2 Yes Details →
v6.4.9 M2 Yes Details →
v6.4.8 M2 Yes Details →
v6.4.7 M2 Yes Details →
v6.4.4 M2 Yes Details →
v6.4.3 M2 Yes Details →
v6.4.0 M2 Yes Details →
v6.4.0-RC2 M2 Yes Details →
v6.4.0-RC1 M2 Yes Details →
v6.4.0-BETA3 M2 Yes Details →
v6.4.0-BETA1 M2 Yes Details →
v6.3.12 M2 Yes Details →
v6.3.8 M2 Yes Details →
v6.3.6 M2 Yes Details →
v6.3.5 M2 Yes Details →
v6.3.4 M2 Yes Details →
v6.3.2 M2 Yes Details →
v6.3.1 M2 Yes Details →
v6.3.0 M2 Yes Details →
v6.3.0-RC1 M1 Yes Details →
v6.3.0-BETA1 M1 Yes Details →
v6.2.13 M1 Yes Details →
v6.2.11 M1 Yes Details →
v6.2.10 M1 Yes Details →
v6.2.8 M1 Yes Details →
v6.2.7 M1 Yes Details →
v6.2.6 M1 Yes Details →
v6.2.5 M1 Yes Details →
v6.2.2 M1 Yes Details →
v6.2.0 M1 Yes Details →
v6.2.0-RC1 M1 Yes Details →
v6.2.0-BETA3 M1 Yes Details →
v6.2.0-BETA1 M1 Yes Details →
v6.1.12 M1 Yes Details →
v6.1.11 M1 Yes Details →
v6.1.9 M1 Yes Details →
v6.1.7 M1 Yes Details →
v6.1.6 M1 Yes Details →
v6.1.5 M1 Yes Details →
v6.1.4 M1 Yes Details →
v6.1.3 M1 Yes Details →
v6.1.2 M1 Yes Details →
v6.1.1 M1 Yes Details →
v6.1.0 M1 Yes Details →
v6.1.0-RC1 M1 Yes Details →
v6.1.0-BETA2 M1 Yes Details →

Newest 120 of 619 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
  • 2021 2
  • 2022 2
  • 2023 1
  • 2024 2
  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 13 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/security-http

Is symfony/security-http safe to use?

Vulert records 13 vulnerabilities for symfony/security-http in Packagist: 0 critical, 5 high, 7 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-http have?

13 vulnerabilities are recorded for symfony/security-http in the Packagist ecosystem: 0 critical, 5 high, 7 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-http vulnerabilities disclosed?

4 vulnerabilities were recorded for symfony/security-http in the last 12 months, and the oldest entry in this database dates to 02 Dec 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/security-http 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-http for upcoming vulnerabilities?

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