Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-qjfw-cvjf-f4fm

HIGHFix: amphp/http@3a33e68

GHSA-qjfw-cvjf-f4fm is a high-severity (CVSS 8.2) vulnerability in amphp/http. O3 Security confirms whether GHSA-qjfw-cvjf-f4fm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

AMPHP Denial of Service via HTTP/2 CONTINUATION Frames

Also known asCVE-2024-2653
Published
Apr 3, 2024
Updated
Jul 8, 2026
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed

Real-World Exposure

3 pkgs affected
🐘amphp/http🐘amphp/http🐘amphp/http-client

Real-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

amphp/http 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. amphp/http-client and amphp/http-server are indirectly affected if they're used with an unpatched version of amphp/http. Early versions of amphp/http-client with HTTP/2 support (v4.0.0-rc10 to 4.0.0) are also directly affected.

Acknowledgements

Thank you to Bartek Nowotarski for reporting the vulnerability.

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistamphp/http2.0.0&&< 2.1.12.1.1
🐘Packagistamphp/httpall versions1.7.3
🐘Packagistamphp/http-client4.0.0-rc10No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for amphp/http. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update amphp/http to 2.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qjfw-cvjf-f4fm is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-qjfw-cvjf-f4fm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-qjfw-cvjf-f4fm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

`amphp/http` 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. `amphp/http-client` and `amphp/http-server` are indirectly affected if they're used with an unpatched version of `amphp/http`. Early versions of `amphp/http-client` with HTTP/2 support (v4.0.0-rc10 to 4.0.0) are also directly affected. ## Acknowledgements Thank you to [Bartek Nowotarski](https://nowotarski.info/) for reporting the vulnerability.
O3 Security · Impact-Aware SCA

Is GHSA-qjfw-cvjf-f4fm in your dependencies?

O3 detects GHSA-qjfw-cvjf-f4fm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.