CVE-2024-27983

Original summary

Normalized public record · Updated Nov 3, 2026

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.

Publisher and source text is retained separately from QFinch interpretation.

Affected products

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

1. Confirm the affected product and reachable code path exist in your environment.
2. Apply the vendor-supported patch or mitigation from the primary advisory.
3. Rescan the exact deployed revision and retain verification evidence.

Evidence coverage

SSVC priority

MEDIUM

Confidence

Not available

Aliases

None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

1. hackerone.com ↗
2. lists.fedoraproject.org ↗
3. lists.fedoraproject.org ↗
4. www.openwall.com ↗
5. security.netapp.com ↗
6. lists.debian.org ↗
7. www.kb.cert.org ↗

Record history

Published Apr 9, 2024 · Last refreshed Nov 3, 2026