CVE-2024-27983

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

84.4% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2024-02-29 01:04 UTC ReservedThe CVE id was reserved by its CNA
2. 2024-04-09 01:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 07:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 84.4% in the next 30 days (EPSS).
• Severity: 8.2 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2024-04-09 01:15 UTC

Last modified

2026-06-17 07:20 UTC

Exploit probability

84.4% · EPSS, next 30 days

Weakness

CWE-362 · Race condition

Record status

Deferred

Attack profile CVSS 3.0 · 8.2

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-27983.md and follow it. Check whether this project is affected by CVE-2024-27983. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge