VulertSecurity VulertSecurity

Vulnerability Database · Packagist · Package report

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

amphp/http-client is a package in the Packagist ecosystem. Vulert records 2 vulnerabilities for it across 10 releases, from Apr 2024 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 H1 M1
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.

See all amphp/http-client vulnerabilities

Vulert verdict on amphp/http-client i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, 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 1 year · 0 in the last year i
  • Latest disclosure 15 May 2024 i
  • Highest CVSS 8.2 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 amphp/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
v4.3.1 M1 Yes Details →
v4.3.0 M1 Yes Details →
v4.2.2 M1 Yes Details →
v4.2.1 M1 Yes Details →
v4.2.0 M1 Yes Details →
v4.1.0 M1 Yes Details →
v4.1.0-rc1 M1 Yes Details →
v4.0.0 H1 M1 Yes Details →
v4.0.0-rc11 H1 Yes Details →
v4.0.0-rc10 H1 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service via HTTP/2 CONTINUATION Frames in amphp/http-client 8.2 high 4.1.0-rc1 03 Apr 2024
Header Leakage on Cross-Domain Redirects in amphp/http-client 4.0 medium 4.4.0 15 May 2024

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

Is amphp/http-client safe to use?

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

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

0 vulnerabilities were recorded for amphp/http-client in the last 12 months, and the oldest entry in this database dates to 03 Apr 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 amphp/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 amphp/http-client for upcoming vulnerabilities?

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