CVE-2024-27983

HIGHNVD 8.29.0▲
EchelonGraph scoreHIGH confidence

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

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

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.0(high)
EG Risk
90(Track)
EG Risk 90/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%
Exploitation87% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

April 9, 2024

Last Modified

April 15, 2026

References (12)

Vendor Advisories for CVE-2024-27983(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFixed in / 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.

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoClirantal/CVE-2024-27983-nodejs-http2
    First seen 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 ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-27983?
CVE-2024-27983 is a high vulnerability 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 CVE-2024-27983 disclosed?
CVE-2024-27983 was first published in the National Vulnerability Database on April 9, 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-27983 actively exploited?
CVE-2024-27983 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-27983?
CVE-2024-27983 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-27983?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-27983, 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-27983

Explore →

Is Your Infrastructure Affected by CVE-2024-27983?

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

Start Free Scan →Browse All CVEs