CVE-2026-48937
Received Received - Intake
HTTP/2 GOAWAY Handling DoS in Node.js

Publication date: 2026-06-18

Last updated on: 2026-06-18

Assigner: HackerOne

Description
A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js 22** and **Node.js 24**.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-18
Last Modified
2026-06-18
Generated
2026-06-19
AI Q&A
2026-06-18
EPSS Evaluated
N/A
NVD
CVE-2026-48937
EUVD
EUVD-2026-37928
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
nodejs node.js 22
nodejs node.js 24
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a flaw in the Node.js HTTP/2 server API where the server continues to accept data even after it has sent a GOAWAY frame. The GOAWAY frame is intended to signal the termination of a connection, but due to this flaw, the server improperly keeps accepting data.

It affects two supported Node.js release lines: Node.js 22 and Node.js 24.

Impact Analysis

The vulnerability can impact you by causing the server to continue processing data even after it should have stopped, potentially leading to resource exhaustion or denial of service conditions.

According to the CVSS score of 5.3 (medium severity), the impact is limited to availability (A:L), meaning it can degrade or interrupt service but does not affect confidentiality or integrity.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-48937. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart