CVE-2024-27983

CRITICALNVD 8.29.0
EchelonGraph scoreHIGH confidence

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

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

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

Also known asEUVD-2024-25157 (ENISA EUVD) · GHSA-j65r-8hrg-qc6x (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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 84%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 84%CVSS: 8.2Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP connection is abruptly closed by the client triggering the Http2Session destructor while header frames are still being processed (and stored in memory) causing a race condition.

CVSS v3
8.2
EG Score
9.0CRITICALhigh confidence
EG Risk
86
EG Risk 86/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation84% × 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
84%
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 (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 8.2 HIGH): a likelihood of exploitation, not impact.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
84% within 30 daysSource: FIRST EPSS. 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 9, 2024

Last Modified

April 15, 2026

Advisory Details (6)

Auto-updated Sep 9, 2026
Patch available.
Web page

[SECURITY] Fedora 39 Update: nodejs20-20.12.2-1.fc39 - package-announce - Fedora mailing-lists

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

[SECURITY] Fedora 40 Update: nodejs20-20.12.2-1.fc40 - package-announce - Fedora mailing-lists

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

[SECURITY] [DLA 3886-1] nodejs security update

https://lists.debian.org/debian-lts-announce/2024/09/msg00029.html
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

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs:18-8080020240621122004.63b345852024-07-24redhat
redhatnodejs:16-8080020240510090838.63b345852024-07-08redhat
redhatnodejs:16-8060020240515105144.ad008a3a2024-06-03redhat
redhatnodejs-1:16.20.2-6.el9_02024-06-03redhat
redhatnodejs:18-9020020240516091141.rhel92024-06-03redhat
redhatrh-nodejs14-nodejs-0:14.21.3-7.el72024-05-29redhat
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-9040020240422140329.rhel92024-05-09redhat
redhatnodejs:20-8090020240422150739.a75119d52024-05-09redhat
redhatnodejs:18-8090020240429131734.a75119d52024-05-09redhat

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

(18 across 12 ecosystems)
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.20(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 20.12.1-r0: fixed in 20.12.1-r0
—
nodejs-current—
  • every version up to 21.7.2-r0: fixed in 21.7.2-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.20.1-r0: fixed in 18.20.1-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.20.1-r0: fixed in 18.20.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs12.21.0~dfsg-5 ... 12.22.9~dfsg-1 (19 versions)
  • every version up to 12.22.12~dfsg-1~deb11u5: fixed in 12.22.12~dfsg-1~deb11u5
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs18.13.0+dfsg1-1 ... 18.20.1+dfsg-4 (20 versions)
  • every version up to 18.20.4+dfsg-1~deb12u1: fixed in 18.20.4+dfsg-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.20.1+dfsg-1: fixed in 18.20.1+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs—
  • every version up to 18.20.1+dfsg-1: fixed in 18.20.1+dfsg-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 15× in last 7d / 69× 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 230 rows on record for this CVE.

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. None are among the latest 100 rows. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoClirantal/CVE-2024-27983-nodejs-http2
    Published Apr 14, 2024

    CVE-2024-27983 this repository builds up a vulnerable HTTP2 Node.js server (`server-nossl.js`) based on CVE-2024-27983 which exploits a continuation flood vulnerability in HTTP2 servers.

    Open source ↗

Frequently asked(5)

What is CVE-2024-27983?
CVE-2024-27983 is a critical-severity vulnerability; its CVE record was published on April 9, 2024. An attacker can make the Node.js HTTP/2 server completely unavailable by sending a small amount of HTTP/2 frames packets with a few HTTP/2 frames inside. It is possible to leave some data in nghttp2 memory after reset when headers with HTTP/2 CONTINUATION frame are sent to the server and then a TCP…
When was the CVE record for CVE-2024-27983 published?
The CVE record for CVE-2024-27983 was published on April 9, 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-27983 actively exploited?
CVE-2024-27983 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 84% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-27983?
CVE-2024-27983 has a CVSS v3 base score of 8.2 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2024-27983?
A fix for CVE-2024-27983 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27983 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-27983

Explore →

Is Your Infrastructure Affected by CVE-2024-27983?

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