GHSA-w8gf-g2vq-j2f4 — amphp/http-client
HIGHGHSA-w8gf-g2vq-j2f4 is a high-severity (CVSS 8.2) vulnerability in amphp/http-client. A fix is available for amphp/http-client — see the affected versions and patch details below.
amphp/http-client Denial of Service via HTTP/2 CONTINUATION Frames
Real-World Exposure
amphp/http-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Early versions of amphp/http-client with HTTP/2 support (v4.0.0-rc10 to 4.0.0) will collect HTTP/2 CONTINUATION frames in an unbounded buffer and will not check the header size limit until it has received the END_HEADERS flag, resulting in an OOM crash. Later versions of amphp/http-client (v4.1.0-rc1 and up) depend on amphp/http for HTTP/2 processing and will therefore need an updated version of amphp/http, see GHSA-qjfw-cvjf-f4fm.
Acknowledgements
Thank you to Bartek Nowotarski for reporting the vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | amphp/http-client | ≥ 4.0.0-rc10&&< 4.1.0-rc1 | 4.1.0-rc1composer require amphp/http-client:^4.1.0-rc1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amphp/http-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update amphp/http-client to 4.1.0-rc1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w8gf-g2vq-j2f4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w8gf-g2vq-j2f4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-w8gf-g2vq-j2f4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w8gf-g2vq-j2f4 in your dependencies?
O3 Security finds GHSA-w8gf-g2vq-j2f4 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.