Vulnerability Database · Packagist · Package report

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

symfony/http-client is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Nov 2024 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
2 vulnerabilities recorded M1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 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/http-client 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 2 vulnerabilities on record across 1 year, 1 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 1 year · 1 in the last year i
  • Latest disclosure 15 Jun 2026 i
  • Highest CVSS 6.3 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/http-client, 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
v5.4.49 M1 Yes Details →
v5.4.48 M1 Yes Details →
v5.4.47 M1 Yes Details →
v5.4.46 M1 L1 Yes Details →
v5.4.45 M1 L1 Yes Details →
v5.4.44 M1 L1 Yes Details →
v5.4.43 M1 L1 Yes Details →
v5.4.42 M1 L1 Yes Details →
v5.4.41 M1 L1 Yes Details →
v5.4.40 M1 L1 Yes Details →
v5.4.39 M1 L1 Yes Details →
v5.4.38 M1 L1 Yes Details →
v5.4.37 M1 L1 Yes Details →
v5.4.36 M1 L1 Yes Details →
v5.4.35 M1 L1 Yes Details →
v5.4.34 M1 L1 Yes Details →
v5.4.31 M1 L1 Yes Details →
v5.4.29 M1 L1 Yes Details →
v5.4.26 M1 L1 Yes Details →
v5.4.25 M1 L1 Yes Details →
v5.4.24 M1 L1 Yes Details →
v5.4.23 M1 L1 Yes Details →
v5.4.22 M1 L1 Yes Details →
v5.4.21 M1 L1 Yes Details →
v5.4.20 M1 L1 Yes Details →
v5.4.19 M1 L1 Yes Details →
v5.4.17 M1 L1 Yes Details →
v5.4.16 M1 L1 Yes Details →
v5.4.15 M1 L1 Yes Details →
v5.4.14 M1 L1 Yes Details →
v5.4.13 M1 L1 Yes Details →
v5.4.12 M1 L1 Yes Details →
v5.4.11 M1 L1 Yes Details →
v5.4.9 M1 L1 Yes Details →
v5.4.8 M1 L1 Yes Details →
v5.4.7 M1 L1 Yes Details →
v5.4.5 M1 L1 Yes Details →
v5.4.3 M1 L1 Yes Details →
v5.4.2 M1 L1 Yes Details →
v5.4.1 M1 L1 Yes Details →
v5.4.0 M1 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.14 L1 Yes Details →
v5.3.13 L1 Yes Details →
v5.3.11 L1 Yes Details →
v5.3.10 L1 Yes Details →
v5.3.8 L1 Yes Details →
v5.3.7 L1 Yes Details →
v5.3.4 L1 Yes Details →
v5.3.3 L1 Yes Details →
v5.3.2 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-BETA1 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 →
v5.2.8 L1 Yes Details →
v5.2.7 L1 Yes Details →
v5.2.6 L1 Yes Details →
v5.2.4 L1 Yes Details →
v5.2.3 L1 Yes Details →
v5.2.2 L1 Yes Details →
v5.2.1 L1 Yes Details →
v5.2.0 L1 Yes Details →
v5.2.0-RC2 L1 Yes Details →
v5.2.0-RC1 L1 Yes Details →
v5.2.0-BETA3 L1 Yes Details →
v5.2.0-BETA2 L1 Yes Details →
v5.2.0-BETA1 L1 Yes Details →
v5.1.11 L1 Yes Details →
v5.1.10 L1 Yes Details →
v5.1.9 L1 Yes Details →
v5.1.8 L1 Yes Details →
v5.1.7 L1 Yes Details →
v5.1.6 L1 Yes Details →
v5.1.5 L1 Yes Details →
v5.1.4 L1 Yes Details →
v5.1.3 L1 Yes Details →
v5.1.2 L1 Yes Details →
v5.1.1 L1 Yes Details →
v5.1.0 L1 Yes Details →
v5.1.0-RC2 L1 Yes Details →
v5.1.0-RC1 L1 Yes Details →
v5.1.0-BETA1 L1 Yes Details →
v5.0.11 L1 Yes Details →
v5.0.10 L1 Yes Details →
v5.0.9 L1 Yes Details →
v5.0.8 L1 Yes Details →
v5.0.7 L1 Yes Details →
v5.0.6 L1 Yes Details →
v5.0.5 L1 Yes Details →
v5.0.4 L1 Yes Details →
v5.0.3 L1 Yes Details →
v5.0.2 L1 Yes Details →
v5.0.1 L1 Yes Details →
v5.0.0 L1 Yes Details →
v5.0.0-RC1 L1 Yes Details →
v5.0.0-BETA2 L1 Yes Details →
v5.0.0-BETA1 L1 Yes Details →
v4.4.51 L1 Yes Details →
v4.4.49 L1 Yes Details →
v4.4.47 L1 Yes Details →
v4.4.46 L1 Yes Details →
v4.4.45 L1 Yes Details →
v4.4.44 L1 Yes Details →
v4.4.42 L1 Yes Details →
v4.4.41 L1 Yes Details →
v4.4.40 L1 Yes Details →
v4.4.39 L1 Yes Details →
v4.4.38 L1 Yes Details →
v4.4.37 L1 Yes Details →
v4.4.36 L1 Yes Details →
v4.4.35 L1 Yes Details →
v4.4.34 L1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for symfony/http-client

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/http-client

Is symfony/http-client safe to use?

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

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

1 vulnerability was recorded for symfony/http-client in the last 12 months, and the oldest entry in this database dates to 06 Nov 2024. 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/http-client 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/http-client for upcoming vulnerabilities?

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