Is amphp/http-server 3.2 vulnerable?

Composer · 1 release from 3.2.0 to 3.2.0 · latest amphp/http-server is 3.4.9 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. amphp/http-server 3.2.0, the last 3.2 release, is affected by 1 known security advisory (1 medium). Upgrade to 3.4.4 or later to fix all of them.

Upgrade with:composer require amphp/http-server:^3.4.4

Is your project on an affected amphp/http-server?

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-server 3.2.0

  • MediumGHSA-8grv-jq2g-cfhw10 Feb 2026

    amphp/http-server affected by HTTP/2 DDoS vulnerability

    Affected
    >=3.0.0-beta.1 <3.4.4 · >=2.0.0-rc1 <2.1.10
    Fixed in
    2.1.10, 3.4.4

Which of your client projects are still on amphp/http-server 3.2?

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

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