Vulnerability Database · Packagist · Package report

guzzlehttp/psr7: vulnerability history, versions and safety

guzzlehttp/psr7 is a package in the Packagist ecosystem. Vulert records 6 vulnerabilities for it across 63 releases, from Mar 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded M6
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 21 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on guzzlehttp/psr7 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 6 vulnerabilities on record across 4 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 6 over 4 years · 4 in the last year i
  • Latest disclosure 21 Jul 2026 i
  • Highest CVSS 5.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 guzzlehttp/psr7, 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.12.2 M1 Yes Details →
2.12.1 M1 Yes Details →
2.12.0 M2 Yes Details →
2.11.1 M2 Yes Details →
2.11.0 M2 Yes Details →
2.10.4 M2 Yes Details →
2.10.3 M2 Yes Details →
2.10.2 M2 Yes Details →
2.10.1 M4 Yes Details →
2.10.0 M4 Yes Details →
2.9.1 M4 Yes Details →
2.9.0 M4 Yes Details →
2.8.1 M4 Yes Details →
2.8.0 M4 Yes Details →
2.7.1 M4 Yes Details →
2.7.0 M4 Yes Details →
2.6.3 M4 Yes Details →
2.6.2 M4 Yes Details →
2.6.1 M4 Yes Details →
2.6.0 M4 Yes Details →
2.5.1 M4 Yes Details →
2.5.0 M4 Yes Details →
2.4.5 M4 Yes Details →
2.4.4 M4 Yes Details →
2.4.3 M4 Yes Details →
2.4.2 M4 Yes Details →
2.4.1 M4 Yes Details →
2.4.0 M4 Yes Details →
2.3.0 M4 Yes Details →
2.2.2 M4 Yes Details →
2.2.1 M4 Yes Details →
2.2.0 M4 Yes Details →
2.1.2 M4 Yes Details →
2.1.1 M4 Yes Details →
2.1.0 M4 Yes Details →
2.0.0 M4 Yes Details →
2.0.0-rc1 M4 Yes Details →
2.0.0-beta1 M4 Yes Details →
1.9.1 M4 Yes Details →
1.9.0 M5 Yes Details →
1.8.5 M5 Yes Details →
1.8.4 M5 Yes Details →
1.8.3 M6 Yes Details →
1.8.2 M6 Yes Details →
1.8.1 M6 Yes Details →
1.8.0 M6 Yes Details →
1.7.0 M6 Yes Details →
1.6.1 M6 Yes Details →
1.6.0 M6 Yes Details →
1.5.2 M6 Yes Details →
1.5.1 M6 Yes Details →
1.5.0 M6 Yes Details →
1.4.2 M6 Yes Details →
1.4.1 M6 Yes Details →
1.4.0 M6 Yes Details →
1.3.1 M6 Yes Details →
1.3.0 M6 Yes Details →
1.2.3 M6 Yes Details →
1.2.2 M6 Yes Details →
1.2.1 M6 Yes Details →
1.2.0 M6 Yes Details →
1.1.0 M6 Yes Details →
1.0.0 M6 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
  • 2023 1
  • 2026 4

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

Is guzzlehttp/psr7 safe to use?

Vulert records 6 vulnerabilities for guzzlehttp/psr7 in Packagist: 0 critical, 0 high, 6 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 guzzlehttp/psr7 have?

6 vulnerabilities are recorded for guzzlehttp/psr7 in the Packagist ecosystem: 0 critical, 0 high, 6 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 guzzlehttp/psr7 vulnerabilities disclosed?

4 vulnerabilities were recorded for guzzlehttp/psr7 in the last 12 months, and the oldest entry in this database dates to 25 Mar 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 guzzlehttp/psr7 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 guzzlehttp/psr7 for upcoming vulnerabilities?

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