CVE-2024-28182

HIGHNVD 5.38.8
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 8.8 because EPSS predicted 82% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2024-25307 (ENISA EUVD)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 82%
CISA-KEV: Not listedEPSS PROB: 82%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

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
8.8HIGHhigh confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation82% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
82%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 5.3 MEDIUM): a likelihood of exploitation, not impact.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
82% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 4, 2024

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Oct 16, 2026
Patch available. Sources: github_commit, github.
GitHub commit

commit 00201ecd8f98 (nghttp2/nghttp2)

Fix landed in nghttp2/nghttp2 commit 00201ecd8f98 — awaiting tagged release

https://github.com/nghttp2/nghttp2/commit/00201ecd8f982da3b67d4f6868af72a1b03b14e0
Web page

oss-security - CERT/CC VU#421644: HTTP/2 CONTINUATION frames can be utilized for DoS attacks

http://www.openwall.com/lists/oss-security/2024/04/03/16
Web page

[SECURITY] Fedora 38 Update: nghttp2-1.52.0-3.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/PXJO2EASHM2OQQLGVDY5ZSO7UVDVHTDK/
Web page

[SECURITY] Fedora 39 Update: nghttp2-1.55.1-5.fc39 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/J6ZMXUGB66VAXDW5J6QSTHM5ET25FGSA/
Web page

[SECURITY] Fedora 40 Update: nghttp2-1.59.0-3.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/AGOME6ZXJG7664IPQNVE3DL67E3YP3HY/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 3804-1] nghttp2 security update

https://lists.debian.org/debian-lts-announce/2024/04/msg00026.html
GitHub advisoryMentions a patch (unverified)

Reading unbounded number of HTTP/2 CONTINUATION frames to cause excessive CPU usage · Advisory · nghttp2/nghttp2 · GitHub

https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q
GitHub commit

commit d71a4668c6be (nghttp2/nghttp2)

Fix landed in nghttp2/nghttp2 commit d71a4668c6be — awaiting tagged release

https://github.com/nghttp2/nghttp2/commit/d71a4668c6bead55805d18810d633fbb98315af9

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunghttp2-server (1.40.0-1ubuntu0.3) @ focal2026-11-02ubuntu
ubuntunghttp2-server (1.59.0-1ubuntu0.1) @ noble2026-11-02ubuntu
redhatnodejs:18-8080020240621122004.63b345852024-07-24redhat
redhatnghttp2-0:1.33.0-4.el8_4.22024-07-23redhat
redhatnodejs-1:16.20.2-9.el9_02024-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:18-9040020240422140329.rhel92024-05-09redhat
redhatnodejs:20-8090020240422150739.a75119d52024-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.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp21.36.0-2, 1.36.0-2+deb10u1, 1.36.0-2+deb10u2
  • every version up to 1.36.0-2+deb10u3: fixed in 1.36.0-2+deb10u3
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp21.43.0-1, 1.43.0-1+deb11u1
  • every version up to 1.43.0-1+deb11u2: fixed in 1.43.0-1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp21.52.0-1, 1.52.0-1+deb12u1
  • every version up to 1.52.0-1+deb12u2: fixed in 1.52.0-1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.61.0-1: fixed in 1.61.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.61.0-1: fixed in 1.61.0-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 181 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
  2. 2026-11-11 17:09 UTCEchelonGraph re-scored
  3. 2026-11-11 17:09 UTCVendor advisory
  4. 2026-11-11 16:34 UTCEPSS rescoreEPSS 82% · 99th percentile
  5. 2026-11-10 16:38 UTCEPSS rescoreEPSS 82% · 99th percentile
  6. 2026-11-09 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
  7. 2026-11-06 16:32 UTCEPSS rescoreEPSS 82% · 99th percentile
  8. 2026-11-04 16:33 UTCEchelonGraph re-scored▼ 0.20
  9. 2026-11-04 16:33 UTCVendor advisory
  10. 2026-11-04 16:32 UTCEPSS rescoreEPSS 82% · 99th percentile
  11. 2026-11-04 11:32 UTCEchelonGraph re-scored
  12. 2026-11-04 11:32 UTCVendor advisory
  13. 2026-11-03 13:49 UTCEchelonGraph re-scored
  14. 2026-11-03 13:49 UTCVendor advisory
  15. 2026-11-02 15:54 UTCVendor advisory
  16. 2026-11-01 18:12 UTCEchelonGraph re-scored
  17. 2026-11-01 18:12 UTCVendor advisory
  18. 2026-10-31 20:30 UTCEchelonGraph re-scored
  19. 2026-10-31 20:30 UTCVendor advisory
  20. 2026-10-31 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  21. 2026-10-30 22:48 UTCEchelonGraph re-scored
  22. 2026-10-30 22:48 UTCVendor advisory
  23. 2026-10-30 01:06 UTCEchelonGraph re-scored
  24. 2026-10-30 01:06 UTCVendor advisory
  25. 2026-10-29 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
Show 72 more
  1. 2026-10-29 03:24 UTCEchelonGraph re-scored
  2. 2026-10-29 03:24 UTCVendor advisory
  3. 2026-10-28 05:42 UTCEchelonGraph re-scored
  4. 2026-10-28 05:42 UTCVendor advisory
  5. 2026-10-27 16:29 UTCEPSS rescoreEPSS 85% · 99th percentile
  6. 2026-10-27 08:00 UTCEchelonGraph re-scored
  7. 2026-10-27 08:00 UTCVendor advisory
  8. 2026-10-26 07:55 UTCVendor advisory
  9. 2026-10-25 17:14 UTCEchelonGraph re-scored
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  11. 2026-10-25 10:13 UTCEchelonGraph re-scored
  12. 2026-10-25 10:13 UTCVendor advisory
  13. 2026-10-24 12:30 UTCEchelonGraph re-scored
  14. 2026-10-24 12:30 UTCVendor advisory
  15. 2026-10-23 14:44 UTCVendor advisory
  16. 2026-10-22 16:58 UTCEchelonGraph re-scored
  17. 2026-10-22 16:58 UTCVendor advisory
  18. 2026-10-22 16:31 UTCEPSS rescoreEPSS 85% · 99th percentile
  19. 2026-10-21 18:27 UTCEchelonGraph re-scored
  20. 2026-10-21 18:27 UTCVendor advisory
  21. 2026-10-21 16:29 UTCEPSS rescoreEPSS 85% · 99th percentile
  22. 2026-10-20 20:44 UTCEchelonGraph re-scored
  23. 2026-10-20 20:44 UTCVendor advisory
  24. 2026-10-20 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  25. 2026-10-19 23:03 UTCEchelonGraph re-scored
  26. 2026-10-19 23:03 UTCVendor advisory
  27. 2026-10-18 22:27 UTCEchelonGraph re-scored
  28. 2026-10-18 22:27 UTCVendor advisory
  29. 2026-10-18 07:21 UTCEchelonGraph re-scored
  30. 2026-10-18 00:25 UTCEchelonGraph re-scored
  31. 2026-10-18 00:25 UTCVendor advisory
  32. 2026-10-17 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  33. 2026-10-17 02:25 UTCEchelonGraph re-scored
  34. 2026-10-17 02:25 UTCVendor advisory
  35. 2026-10-16 04:11 UTCEchelonGraph re-scored
  36. 2026-10-16 04:11 UTCVendor advisory
  37. 2026-10-15 01:19 UTCEchelonGraph re-scored
  38. 2026-10-15 01:19 UTCVendor advisory
  39. 2026-10-14 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  40. 2026-10-13 16:30 UTCEPSS rescoreEPSS 85% · 99th percentile
  41. 2026-10-12 17:58 UTCEchelonGraph re-scored
  42. 2026-10-11 21:22 UTCEchelonGraph re-scored
  43. 2026-10-11 16:16 UTCEchelonGraph re-scored
  44. 2026-10-11 15:36 UTCOSV refresh
  45. 2026-10-09 20:05 UTCEPSS rescoreEPSS 85% · 99th percentile
  46. 2026-10-08 17:07 UTCEPSS rescoreEPSS 85% · 99th percentile
  47. 2026-10-07 23:46 UTCEPSS rescoreEPSS 85% · 99th percentile
  48. 2026-10-05 17:41 UTCEPSS rescoreEPSS 85% · 99th percentile
  49. 2026-10-01 19:48 UTCEPSS rescoreEPSS 85% · 99th percentile
  50. 2026-09-30 17:01 UTCEchelonGraph re-scored
  51. 2026-09-27 13:43 UTCEPSS rescoreEPSS 85% · 99th percentile
  52. 2026-09-26 15:57 UTCEPSS rescoreEPSS 85% · 99th percentile
  53. 2026-09-26 00:23 UTCEPSS rescoreEPSS 85% · 99th percentile
  54. 2026-09-24 14:01 UTCEPSS rescoreEPSS 85% · 99th percentile
  55. 2026-09-23 13:46 UTCEPSS rescoreEPSS 85% · 99th percentile
  56. 2026-09-22 14:46 UTCEPSS rescoreEPSS 85% · 99th percentile
  57. 2026-09-22 03:16 UTCOSV refresh
  58. 2026-09-18 19:26 UTCEPSS rescoreEPSS 85% · 99th percentile
  59. 2026-09-16 14:06 UTCEPSS rescoreEPSS 85% · 99th percentile
  60. 2026-09-12 14:59 UTCEPSS rescoreEPSS 85% · 99th percentile
  61. 2026-09-06 13:46 UTCEPSS rescoreEPSS 85% · 99th percentile
  62. 2026-09-05 15:26 UTCEPSS rescoreEPSS 85% · 99th percentile
  63. 2026-09-04 05:05 UTCEPSS rescoreEPSS 85% · 99th percentile
  64. 2026-09-03 00:59 UTCOSV refresh
  65. 2026-09-02 14:10 UTCEPSS rescoreEPSS 85% · 99th percentile
  66. 2026-08-30 19:15 UTCEPSS rescoreEPSS 85% · 99th percentile
  67. 2026-08-30 01:20 UTCEPSS rescoreEPSS 85% · 99th percentile
  68. 2026-08-28 21:39 UTCEPSS rescoreEPSS 85% · 99th percentile
  69. 2026-08-27 14:23 UTCEPSS rescoreEPSS 85% · 99th percentile
  70. 2026-08-24 14:15 UTCEPSS rescoreEPSS 85% · 99th percentile
  71. 2026-08-21 23:47 UTCEPSS rescoreEPSS 85% · 99th percentile
  72. 2026-08-19 17:02 UTCEPSS rescoreEPSS 85% · 99th percentile

Frequently asked(5)

What is CVE-2024-28182?
CVE-2024-28182 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2024-28182 published?
The CVE record for CVE-2024-28182 was published on April 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-28182 actively exploited?
CVE-2024-28182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 82% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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 + FIRST EPSS into a combined EG score of 8.8 (HIGH).
How do I remediate CVE-2024-28182?
A fix for CVE-2024-28182 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-28182 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.