Is amphp/http 1.6 vulnerable?

Composer · 4 releases from 1.6.0 to 1.6.3 · latest amphp/http is 2.1.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. amphp/http 1.6.3, the last 1.6 release, is affected by 1 known security advisory (1 high), including CVE-2024-2653. Upgrade to 1.7.3 or later to fix all of them.

Upgrade with:composer require amphp/http:^1.7.3

Is your project on an affected amphp/http?

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

Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting amphp/http 1.6.3

  • HighCVE-2024-2653GHSA-qjfw-cvjf-f4fm3 Apr 2024

    AMPHP Denial of Service via HTTP/2 CONTINUATION Frames

    Affected
    >=2.0.0 <2.1.1 · <1.7.3
    Fixed in
    1.7.3, 2.1.1

Every amphp/http 1.6.x release

Affected: 1.6.0 to 1.6.3. Latest amphp/http: 2.1.2.

VersionKnown advisories
amphp/http 1.6.3CVE-2024-2653
amphp/http 1.6.2CVE-2024-2653
amphp/http 1.6.1CVE-2024-2653
amphp/http 1.6.0CVE-2024-2653

Which of your client projects are still on amphp/http 1.6?

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

Other amphp/http 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.