Is amphp/http 2.1 vulnerable?
Composer · 3 releases from 2.1.0 to 2.1.2 · latest amphp/http is 2.1.2 · checked 18 Nov 2026
No known advisories in the last release
amphp/http 2.1.2, the last 2.1 release, has no known advisories. 1 advisory affects earlier 2.1.x releases, so update to 2.1.2.
composer require amphp/http:^2.1.2Is your project on an affected amphp/http?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.1.x, affecting earlier releases
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 2.1.x release
Affected: 2.1.0. 2.1.1 and later are not affected.
| Version | Known advisories |
|---|---|
| amphp/http 2.1.2 | None |
| amphp/http 2.1.1 | None |
| amphp/http 2.1.0 | CVE-2024-2653 |
Which of your client projects are still on amphp/http 2.1?
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.