Is guzzlehttp/guzzle 8.0 vulnerable?

Composer · 4 releases from 8.0.0 to 8.0.3 · latest guzzlehttp/guzzle is 8.3.1 · checked 1 Nov 2026

No known advisories in the last release

guzzlehttp/guzzle 8.0.3, the last 8.0 release, has no known advisories. 2 advisories affect earlier 8.0.x releases, so update to 8.0.3.

Update within 8.0:composer require guzzlehttp/guzzle:^8.0.3

Is your project affected?

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

Fixed within 8.0.x, affecting earlier releases

  • HighCVE-2026-69246GHSA-v5mv-p594-2x333 Aug 2026

    Guzzle: Noncanonical host can bypass host-based checks

    Affected
    <7.15.2 · >=8.0.0 <8.0.1
    Fixed in
    7.15.2, 8.0.1
  • MediumCVE-2026-69245GHSA-f7vp-7xgx-4w4r3 Aug 2026

    Guzzle: Noncanonical cookie domain keeps subdomain scope

    Affected
    <7.15.2 · >=8.0.0 <8.0.1
    Fixed in
    7.15.2, 8.0.1

Which of your client projects are still on guzzlehttp/guzzle 8.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact guzzlehttp/guzzle 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/guzzle 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.