CVE-2024-2653

HIGHNVD 8.29.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 83% probability of exploitation within the next 30 days (top 0.4% of all CVEs). NVD baseline CVSS 8.2 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.2
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
CISA-KEV: Not listedEPSS: 83%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

amphp/http will collect CONTINUATION frames in an unbounded buffer and will not check a limit until it has received the set END_HEADERS flag, resulting in an OOM crash.

CVSS v3
8.2
EG Score
9.0(high)
EG Risk
89(Track)
EG Risk 89/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation83% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.6%
KEV
Not listed

Published

April 3, 2024

Last Modified

April 15, 2026

Affected Packages

(2 across 1 ecosystem)
Packagist(2)
PackageVulnerable rangeFixed inDependents
amphp/httpv1.0.0 ... v1.7.2 (15 versions)1.7.3
amphp/http-clientv4.0.0, v4.0.0-rc10, v4.0.0-rc11

Data Freshness Timeline

(refreshed 4× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:34 UTCEG score recompute 0.80
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-20 17:06 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 01:59 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-12 05:45 UTCEPSS rescore
  10. 2026-07-11 08:22 UTCOSV refresh
  11. 2026-07-09 19:09 UTCEPSS rescore
  12. 2026-07-04 06:30 UTCEPSS rescore
  13. 2026-07-01 15:05 UTCEPSS rescore
  14. 2026-06-28 04:55 UTCEPSS rescore
  15. 2026-06-28 04:55 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-23 21:32 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-18 17:51 UTCEPSS rescore
  24. 2026-06-17 17:52 UTCEPSS rescore
  25. 2026-06-17 17:52 UTCEPSS rescore
Show 64 more
  1. 2026-06-15 17:47 UTCEPSS rescore
  2. 2026-06-14 23:16 UTCEPSS rescore
  3. 2026-06-13 22:59 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-12 23:11 UTCEPSS rescore
  6. 2026-06-12 23:11 UTCEPSS rescore
  7. 2026-06-11 13:59 UTCEPSS rescore
  8. 2026-06-10 22:17 UTCEPSS rescore
  9. 2026-06-10 13:21 UTCEPSS rescore
  10. 2026-06-10 13:21 UTCEPSS rescore
  11. 2026-06-08 14:16 UTCEPSS rescore
  12. 2026-06-07 15:24 UTCEPSS rescore
  13. 2026-06-07 15:24 UTCEPSS rescore
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-06 13:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-05 22:46 UTCEPSS rescore
  18. 2026-06-05 06:09 UTCEPSS rescore
  19. 2026-06-05 06:09 UTCEPSS rescore
  20. 2026-06-04 13:11 UTCEPSS rescore
  21. 2026-06-04 13:11 UTCEPSS rescore
  22. 2026-06-04 13:11 UTCEPSS rescore
  23. 2026-06-02 20:12 UTCEPSS rescore
  24. 2026-06-02 20:12 UTCEPSS rescore
  25. 2026-06-01 13:51 UTCEPSS rescore
  26. 2026-06-01 13:51 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-05-31 22:30 UTCEPSS rescore
  29. 2026-05-31 22:30 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-29 13:43 UTCEPSS rescore
  33. 2026-05-29 13:43 UTCEPSS rescore
  34. 2026-05-28 13:44 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-28 13:44 UTCEPSS rescore
  37. 2026-05-27 13:40 UTCEPSS rescore
  38. 2026-05-27 13:40 UTCEPSS rescore
  39. 2026-05-26 13:43 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 07:18 UTCEPSS rescore
  42. 2026-05-26 07:18 UTCEPSS rescore
  43. 2026-05-22 21:16 UTCEPSS rescore
  44. 2026-05-22 21:16 UTCEPSS rescore
  45. 2026-05-22 21:16 UTCEPSS rescore
  46. 2026-05-22 21:16 UTCEPSS rescore
  47. 2026-05-22 03:37 UTCEG score recompute
  48. 2026-05-21 22:42 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 22:37 UTCEPSS rescore
  53. 2026-05-20 22:37 UTCEPSS rescore
  54. 2026-05-20 11:21 UTCEPSS rescore
  55. 2026-05-20 11:21 UTCEPSS rescore
  56. 2026-05-20 11:21 UTCEPSS rescore
  57. 2026-05-20 11:21 UTCEPSS rescore
  58. 2026-05-20 11:21 UTCEPSS rescore
  59. 2026-05-20 06:03 UTCOSV refresh
  60. 2026-05-18 21:30 UTCEPSS rescore
  61. 2026-05-18 21:30 UTCEPSS rescore
  62. 2026-05-18 21:30 UTCEPSS rescore
  63. 2026-05-18 21:30 UTCEPSS rescore
  64. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-2653?
CVE-2024-2653 is a high vulnerability published on April 3, 2024. amphp/http will collect CONTINUATION frames in an unbounded buffer and will not check a limit until it has received the set END_HEADERS flag, resulting in an OOM crash.
When was CVE-2024-2653 disclosed?
CVE-2024-2653 was first published in the National Vulnerability Database on April 3, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-2653 actively exploited?
CVE-2024-2653 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-2653?
CVE-2024-2653 has a CVSS v3 base score of 8.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-2653?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-2653, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-2653

Explore →

Is Your Infrastructure Affected by CVE-2024-2653?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.