Is amphp/http-server 3.4 vulnerable?

Composer · 10 releases from 3.4.0 to 3.4.9 · latest amphp/http-server is 3.4.9 · checked 18 Nov 2026

No known advisories in the last release

amphp/http-server 3.4.9, the last 3.4 release, has no known advisories. 1 advisory affects earlier 3.4.x releases, so update to 3.4.9.

Update within 3.4:composer require amphp/http-server:^3.4.9

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

Fixed within 3.4.x, affecting earlier releases

  • 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

Every amphp/http-server 3.4.x release

Affected: 3.4.0 to 3.4.3. 3.4.4 and later are not affected.

VersionKnown advisories
amphp/http-server 3.4.9None
amphp/http-server 3.4.8None
amphp/http-server 3.4.7None
amphp/http-server 3.4.6None
amphp/http-server 3.4.5None
amphp/http-server 3.4.4None
amphp/http-server 3.4.3GHSA-8grv-jq2g-cfhw
amphp/http-server 3.4.2GHSA-8grv-jq2g-cfhw
amphp/http-server 3.4.1GHSA-8grv-jq2g-cfhw
amphp/http-server 3.4.0GHSA-8grv-jq2g-cfhw

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

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.