Is guzzlehttp/psr7 2.5 vulnerable?

Composer · 2 releases from 2.5.0 to 2.5.1 · latest guzzlehttp/psr7 is 3.2.0 · checked 2 Nov 2026

Yes: 4 known advisories

Yes. guzzlehttp/psr7 2.5.1, the last 2.5 release, is affected by 4 known security advisories (4 medium), including CVE-2026-59882, CVE-2026-55766, CVE-2026-48998. Upgrade to 2.12.3 or later to fix all of them.

Upgrade with:composer require guzzlehttp/psr7:^2.12.3

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting guzzlehttp/psr7 2.5.1

  • MediumCVE-2026-59882GHSA-c2w2-prh8-qm9821 Jul 2026

    guzzlehttp/psr7: Host Confusion via Weak URI Host Validation

    Affected
    <2.12.3
    Fixed in
    2.12.3
  • MediumCVE-2026-55766GHSA-vm85-hxw5-543219 Jun 2026

    guzzlehttp/psr7: CRLF Injection in HTTP Start-Line Serialization

    Affected
    <2.12.1
    Fixed in
    2.12.1
  • MediumCVE-2026-48998GHSA-34xg-wgjx-8xph11 Jun 2026

    guzzlehttp/psr7 has Host Confusion via Authority Reinterpretation

    Affected
    <2.10.2
    Fixed in
    2.10.2
  • MediumCVE-2026-49214GHSA-hq7v-mx3g-29hw11 Jun 2026

    guzzlehttp/psr7 has CRLF Injection via URI Host Component

    Affected
    <2.10.2
    Fixed in
    2.10.2

Which of your client projects are still on guzzlehttp/psr7 2.5?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact guzzlehttp/psr7 version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other guzzlehttp/psr7 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Composer registry. Refreshed daily.