CVE-2024-28182

MEDIUMNVD 5.39.0
EchelonGraph scoreHIGH confidence

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

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

A fix is available — apply it.

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.

CVSS v3
5.3
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%
Exploitation85% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

April 4, 2024

Last Modified

November 4, 2025

References (18)

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunghttp2-server (1.59.0-1ubuntu0.1) @ noble2026-05-24ubuntu
ubuntunghttp2-server (1.30.0-1ubuntu1+esm2) @ bionic2026-05-24ubuntu
redhatnodejs:18-8080020240621122004.63b345852024-07-24redhat
redhatnodejs-1:16.20.2-9.el9_02024-07-23redhat
redhatnghttp2-0:1.33.0-4.el8_4.22024-07-23redhat
redhatnghttp2-0:1.33.0-3.el8_2.32024-07-16redhat
redhatnghttp2-0:1.33.0-6.el8_10.12024-07-02redhat
redhatnghttp2-0:1.43.0-5.el9_0.32024-06-12redhat
redhatnghttp2-0:1.33.0-4.el8_6.22024-06-10redhat
redhatnghttp2-0:1.43.0-5.el9_2.32024-06-06redhat
redhatnghttp2-0:1.33.0-5.el8_8.12024-06-06redhat
redhatnodejs:18-9020020240516091141.rhel92024-06-03redhat
redhatnghttp2-0:1.43.0-5.el9_4.32024-05-30redhat
redhatnodejs-1:16.20.2-5.el9_2.32024-05-21redhat
redhatnodejs-1:16.20.2-8.el9_42024-05-20redhat
redhatnodejs:20-9040020240419140200.rhel92024-05-15redhat
redhatnodejs:18-8090020240429131734.a75119d52024-05-09redhat
redhatnodejs:20-8090020240422150739.a75119d52024-05-09redhat
redhatnodejs:18-9040020240422140329.rhel92024-05-09redhat
redhatjbcs-httpd24-nghttp2-0:1.43.0-13.el7jbcs2024-05-07redhat
redhatpatch2024-05-07redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 5× in last 7d / 23× 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:35 UTCEG score recompute 3.70
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:23 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-14 14:55 UTCOSV refresh
  9. 2026-07-13 06:11 UTCEPSS rescore
  10. 2026-07-11 08:26 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-08 15:13 UTCEPSS rescore
  13. 2026-07-07 13:45 UTCEPSS rescore
  14. 2026-07-07 13:45 UTCEPSS rescore
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 16:26 UTCEPSS rescore
  17. 2026-07-04 06:30 UTCEPSS rescore
  18. 2026-07-01 15:05 UTCEPSS rescore
  19. 2026-06-26 15:39 UTCOSV refresh
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 13:48 UTCEPSS rescore
  22. 2026-06-23 21:32 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
Show 43 more
  1. 2026-06-19 19:25 UTCEPSS rescore
  2. 2026-06-19 19:24 UTCEPSS rescore
  3. 2026-06-17 17:52 UTCEPSS rescore
  4. 2026-06-17 17:52 UTCEPSS rescore
  5. 2026-06-15 17:47 UTCEPSS rescore
  6. 2026-06-14 23:16 UTCEPSS rescore
  7. 2026-06-13 22:59 UTCEPSS rescore
  8. 2026-06-13 22:59 UTCEPSS rescore
  9. 2026-06-12 23:11 UTCEPSS rescore
  10. 2026-06-12 23:11 UTCEPSS rescore
  11. 2026-06-11 13:59 UTCEPSS rescore
  12. 2026-06-10 22:17 UTCEPSS rescore
  13. 2026-06-10 13:21 UTCEPSS rescore
  14. 2026-06-10 13:21 UTCEPSS rescore
  15. 2026-06-08 22:07 UTCOSV refresh
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-06 13:46 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 06:09 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-04 13:11 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:12 UTCEPSS rescore
  27. 2026-06-02 20:12 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-06-01 13:51 UTCEPSS rescore
  30. 2026-06-01 13:51 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-31 00:15 UTCEPSS rescore
  33. 2026-05-29 13:43 UTCEPSS rescore
  34. 2026-05-29 13:43 UTCEPSS rescore
  35. 2026-05-28 13:44 UTCEPSS rescore
  36. 2026-05-28 13:44 UTCEPSS rescore
  37. 2026-05-28 13:44 UTCEPSS rescore
  38. 2026-05-27 13:40 UTCEPSS rescore
  39. 2026-05-27 13:40 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 13:43 UTCEPSS rescore
  42. 2026-05-24 05:12 UTCEG score recompute
  43. 2026-05-24 05:12 UTCVendor advisory

Frequently asked(5)

What is CVE-2024-28182?
CVE-2024-28182 is a medium vulnerability published on April 4, 2024. nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK…
When was CVE-2024-28182 disclosed?
CVE-2024-28182 was first published in the National Vulnerability Database on April 4, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-28182 actively exploited?
CVE-2024-28182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-28182?
CVE-2024-28182 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-28182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-28182, 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

Explore the affected products and dependency analysis for CVE-2024-28182

Explore →

Is Your Infrastructure Affected by CVE-2024-28182?

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